Closed Bug 904322 Opened 11 years ago Closed 11 years ago

[graph server] Do not send regression alerts for known-bad data

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mbrubeck, Assigned: mbrubeck)

References

Details

(Whiteboard: [regression-detection])

Attachments

(3 files, 1 obsolete file)

To reduce noise from false positives on the mailing list, we should add an option to analysis.cfg to temporarily suppress email for datasets that are known to be bad/corrupt, e.g. bug 859571.
Product: mozilla.org → Release Engineering
This reduces duplication, and helps make sure we are testing what we are actually deploying.
Attachment #789629 - Flags: review?(catlee)
Attachment #789630 - Flags: review?(catlee)
Blocks: 908888
Attachment #789629 - Flags: review?(catlee) → review+
Comment on attachment 789630 [details] [diff] [review]
part 2: suppress email for known bad data

Review of attachment 789630 [details] [diff] [review]:
-----------------------------------------------------------------

::: server/analysis/analysis.cfg.template
@@ +24,5 @@
>  ignore_percentage_tests = LibXUL Memory during link
>  
> +# Don't send any email alerts for these subjects (comma-separated list of regexps)
> +suppress_email_subjects = Ts.*Paint.* WINNT 6\.(1|2), ; bug 859571
> +    Tp5 Optimized Responsiveness - WINNT 6\.(1|2), ; bug 751975

doesn't the trailing comma here cause the set of regular expressions to be ["Ts.*Paint.* WINNT 6\.(1|2)", "Tp5 Optimized Responsiveness - WINNT 6\.(1|2)", ""]? And then the empty pattern matches all tests.
(In reply to Chris AtLee [:catlee] from comment #3)
> > +suppress_email_subjects = Ts.*Paint.* WINNT 6\.(1|2), ; bug 859571
> > +    Tp5 Optimized Responsiveness - WINNT 6\.(1|2), ; bug 751975
> 
> doesn't the trailing comma here cause the set of regular expressions to be
> ["Ts.*Paint.* WINNT 6\.(1|2)", "Tp5 Optimized Responsiveness - WINNT
> 6\.(1|2)", ""]? And then the empty pattern matches all tests.

It looks like it's actually picking up "; bug 751975" even though ";" is supposed to begin an inline comment.  (I think the comment parsing in ConfigParser is a bit wonky.)  I'll remove the trailing comma and just use # comments on a separate line.
Addresses issue found in review.
Attachment #789630 - Attachment is obsolete: true
Attachment #789630 - Flags: review?(catlee)
Attachment #795601 - Flags: review?(catlee)
Attachment #795601 - Flags: review?(catlee) → review+
http://hg.mozilla.org/graphs/rev/ae907a51f5f3
http://hg.mozilla.org/graphs/rev/34f664a03e4d
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Note: This requires a change to analysis.cfg in production when it is deployed.
Blocks: 909816
Oops!  I used /Ts.*Paint/ because I wanted to match both "Ts, Paint" and "Ts Paint, (MAX|MED) Dirty Profile" -- but this also matches "tscroll-MozAfterPaint".

This adjusts the regex to use /\bTs\b/ so it won't match "ts" within another word, and adds some more test cases.
Attachment #796366 - Flags: review?(catlee)
Attachment #796366 - Flags: review?(catlee) → review+
Blocks: 751975
Component: Tools → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: