Skip to content

Merge, split and suggestions

Bucketing is automatic, and sometimes it groups failures differently from how you think about the bugs. Two signatures can be the same bug worded by a value the normalization didn't catch, and one signature can hold two different bugs that happen to print the same message. This page shows how to merge signatures, unmerge them, split one apart, and act on DV Forge's Possible duplicates suggestions.

All of these actions need the triager role (see Permissions). Each one takes effect for the failures already recorded and for every future hit, and appears in the signature's activity timeline.

Merge two signatures

Merge when two signatures are really the same bug.

  1. Open the signature you want to fold away (the source).
  2. Select Merge into….
  3. In Find the signature to merge into, search titles in the project. Up to 20 results show, most hits first, each with its classification and hit count.
  4. Select the target. The Confirm merge step shows both titles and their hit counts.
  5. Select Merge. DV Forge opens the target's page.

What a merge does:

  • The target survives. The source's failures move to the target, and its future hits land on the target. The hit, regression and recurrence counts of both are recomputed.
  • The source disappears from lists. Its page stays reachable and shows a banner: "Merged into target. Its failures and new hits are counted there." Its comments, attachments and activity stay on the source's page, which becomes read-only.
  • The target's triage state doesn't change. Status, assignee and labels stay as they were on the target.
  • Split rules keep working. Failures that the source had split off to a child signature still go to that child; new hits on the target also pass through the target's own split rules.
  • Chains are flattened. Signatures that were merged into the source now point straight at the target, and are listed under the target's Merged from.
  • Open merge suggestions about the source are withdrawn.
  • If the source was mapped to a root-cause scenario and the target wasn't, the target takes over the mapping (see Root-cause agent).

You can't merge a signature into itself, and neither signature can already be merged into something else. To merge into a signature that was itself merged away, merge into its survivor instead.

Unmerge a signature

An unmerge restores a merged signature as its own signature: the failures that belong to it come back from the target (and from the target's split children), and its future hits land on it again.

You can unmerge from either page:

  • On the merged signature's page, select Unmerge in the "Merged into" banner.
  • On the target's page, find the signature under Merged from and select Unmerge next to it.

Confirm with Unmerge when asked "Restore title as its own signature?".

Because chains are flattened, unmerging one signature doesn't bring back others that were merged into it before it was merged. Each appears under the survivor's Merged from; unmerge them one by one.

When you can't unmerge

Some merges are made by re-bucketing, not by a person. Those can't be undone, and the page says why instead of offering Unmerge:

You see Why
"Merged by re-bucketing: its failures now share the target's fingerprint, so it can't be unmerged. Split the target instead." After a re-bucket, both signatures' failures have the same fingerprint. Unmerging would restore nothing, so use a split on the target to separate them.
"Re-bucketing gave this signature's fingerprint to another signature, so unmerging would restore nothing." The signature no longer owns a fingerprint of its own.

On the target's Merged from list, these entries show re-bucketed; can't unmerge.

Split a signature

Split when one signature holds failures that are really a different bug. A split creates a child signature and a split rule: failures whose error line contains a piece of text go to the child, now and in the future.

  1. Open the signature and select Split….
  2. In Error line contains…, type the text that tells the two bugs apart (up to 256 characters). It's a case-insensitive substring, not a regular expression: AXI_RESP matches ... axi_resp=SLVERR ....
  3. Optionally, type a New signature title. If you leave it empty, the child is titled with the first matching error line.
  4. Select Preview (or press Enter). DV Forge shows how many failures would move to the new signature and how many stay, with up to five sample matching error lines. Nothing changes yet.
  5. If the preview looks right, select Split off N.

The new child appears under the Split… button as a link. The parent's page lists the rule under Split rules: the substring, a link to the child signature, who created it and when.

Things to know:

  • The text is matched against the error line. For a failure without one, DV Forge matches the headline text instead.
  • A split must leave failures on both sides. If nothing matches, the preview says "Nothing matches — try a different substring." If everything matches, it says "Every failure matches — a split needs some to stay behind."
  • The child starts fresh. It starts Untriaged, with the parent's classification, severity and message id. Its normalized template is the parent's with | contains: <your text> appended.
  • Rules are checked in the order they were created, and the first match wins. A new rule goes after the existing ones.
  • A merged signature can't be split. Split the signature it was merged into.

Undo a split

There's no button to delete a split rule. To undo a split, merge the child back into its parent: the child's failures and future matches return to the parent. If you later need the split again, unmerge the child; running Split… again with the same text is refused while the earlier child is merged away ("an earlier split by this text was merged away; unmerge it first").

Possible duplicates

When new signatures appear (after an upload, or after a re-bucket creates new ones), DV Forge looks for older signatures they probably duplicate. A pair is suggested when the two signatures:

  • have the same severity and message id, and the same bucketing version,
  • are both live (not merged, with hits) and neither is a split child, and
  • have normalized messages that share most of their words: the words the two messages have in common make up at least 80% of all the distinct words in either message (but the messages aren't identical).

Each new signature gets at most five suggestions, best match first.

Suggestions appear on the newer signature's page, in a Possible duplicates card ("Signatures that look like the same bug. Merging keeps the older one."). Each row shows the older signature's title, a % match score, the reason (which words differ: "Same severity and message id; templates differ only in: this one has '…'; the older one has '…'"), the source (suggested by rule) and the older signature's hit count.

  • Merge accepts the suggestion: the newer signature is merged into the older one, and DV Forge opens the older signature. It's an ordinary merge, so you can unmerge it later.
  • Dismiss rejects it. A dismissed pair is never suggested again.

If two people decide the same suggestion at once, the second sees that it's already been decided.

Tip

If you keep merging duplicates that differ only by the same kind of value (a port number, a transaction tag), ask a project admin to add a bucketing mask for it. Future failures then bucket together without anyone merging them.