You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should provide more meaningful error messages when bugs appear to be fixed but are then reproduced during fix bisection (on tip). We could correlate the mismatch between our initial tip attempt and the bisection fix tip attempt. If a mismatch is detected, we should override the bug comment to indicate that the testcase appears to be unreliable.
Testcase crashes using the initial build (mozilla-central 20220129091708-7f00dabac085) but not with tip (mozilla-central 20230127094652-f75c73066b88.)
Unable to bisect testcase (End build crashes!):
Start: 7f00dabac085e45723ccdea1c7e7e2f61e273b30 (20220129091708)
End: f75c73066b887c2379158c73c994b5ef95460238 (20230127094652)
BuildFlags: BuildFlags(asan=False, tsan=False, debug=True, fuzzing=True, coverage=False, valgrind=False, no_opt=False, fuzzilli=False, nyx=False)
Removing bugmon keyword as no further action possible. Please review the bug and re-add the keyword for further analysis.
The text was updated successfully, but these errors were encountered:
We should provide more meaningful error messages when bugs appear to be fixed but are then reproduced during fix bisection (on tip). We could correlate the mismatch between our initial tip attempt and the bisection fix tip attempt. If a mismatch is detected, we should override the bug comment to indicate that the testcase appears to be unreliable.
The text was updated successfully, but these errors were encountered: