Opened 8 years ago

Last modified 6 years ago

#1009 new enhancement

Detect builds that fail consecutively for different reasons

Reported by: ayust Owned by:
Priority: major Milestone: 0.9.+
Version: 0.8.1 Keywords: buildcoord
Cc:

Description

It's possible for a given builder to fail twice in a row, but for completely different reasons. In this case, we probably still want to see problem links in the console for both builds, have it flagged as a new failure, et cetera.

One way to accomplish this would be to allow a step to emit a 'failure signature' when it encounters a failure. This failure signature would be a string that somehow represents a unique cause of failure for the step. (For most steps, this could probably be a hashed version of the error message; for test steps, it might be a hashed version of all of the failing tests.)

When a build fails, its failure signature would be compared to the signature of the build before it, and if it is different, it would be flagged as a 'failed' build instead of a 'failed again' build.

Change History (3)

comment:1 Changed 8 years ago by ayust

  • Summary changed from Add failure signatures to allow detection of builds that fail consecutively for different reasons to Detect builds that fail consecutively for different reasons

comment:2 Changed 8 years ago by dustin

  • Milestone changed from undecided to 0.8.+

This is a pretty cool idea..

comment:3 Changed 6 years ago by dustin

  • Keywords buildcoord added
  • Milestone changed from 0.8.+ to 0.9.+
Note: See TracTickets for help on using tickets.