<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Triage on CodeInstances.com</title>
    <link>https://codeinstances.com/tags/triage/</link>
    <description>Recent content in Triage on CodeInstances.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://codeinstances.com/tags/triage/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CodeInstances Groups Failing Runs by Fingerprint So Repeats of One Bug Show as One</title>
      <link>https://codeinstances.com/codeinstances-groups-failing-runs-by-fingerprint-so-repeats-of-one-bug-show-as-one/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://codeinstances.com/codeinstances-groups-failing-runs-by-fingerprint-so-repeats-of-one-bug-show-as-one/</guid>
      <description>&lt;p&gt;CodeInstances v0.4.0 adds the sixth verb, group. Point &lt;code&gt;codeinstances group&lt;/code&gt; at a folder of instances and it tells you how many different ways your program failed, how often each one happened, and when it was first and last seen.&lt;/p&gt;&#xA;&lt;p&gt;The problem is a familiar one. A nightly job fails 40 times in a week. A flaky suite leaves a pile of red runs. Each failure gets its own instance now, which is good, but 40 files isn&amp;rsquo;t an answer. Usually it&amp;rsquo;s two or three bugs, repeating. Somebody has to open the files, squint at the errors and sort them into piles, and the piles drift, because the messages carry request ids, timestamps and ports that change every time.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
