Closed
Bug 1036325
Opened 11 years ago
Closed 11 years ago
Support bisection for failing intermittent mochitests
Categories
(Testing :: Mochitest, defect)
Testing
Mochitest
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla34
People
(Reporter: vaibhav1994, Assigned: vaibhav1994, Mentored)
References
(Blocks 1 open bug)
Details
Attachments
(1 file, 1 obsolete file)
4.82 KB,
patch
|
vaibhav1994
:
review+
|
Details | Diff | Splinter Review |
This bug is in continuation of bug 1014125 . We need to support bisection for failing intermittent tests. For this, we need to run the failing test 10 times independently and ensure it passes every time.
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → vaibhavmagarwal
Updated•11 years ago
|
Assignee | ||
Comment 1•11 years ago
|
||
Attachment #8461136 -
Flags: review?(jmaher)
Comment 2•11 years ago
|
||
Comment on attachment 8461136 [details] [diff] [review]
intermittent.patch
Review of attachment 8461136 [details] [diff] [review]:
-----------------------------------------------------------------
looking great, and thanks for ensuring you have tested this!
::: testing/mochitest/bisection.py
@@ +259,5 @@
> + self.summary.append("\t\tThe test %s failed." % self.contents['testsToRun'][0])
> + self.failcount += 1
> + self.contents['loop'] = 1
> + self.repeat -= 1
> + if self.failcount < 3:
right here is a hardcoded assumption which we have determined in a closed box as the right solution. Could we make this a variable, say self.maxFailures
set it up on line 16, and then add a comment explaining how it works above where it is defined?
Attachment #8461136 -
Flags: review?(jmaher) → review+
Assignee | ||
Comment 3•11 years ago
|
||
Fixed the nits. Carrying over the r+
Attachment #8461136 -
Attachment is obsolete: true
Attachment #8461570 -
Flags: review+
Assignee | ||
Updated•11 years ago
|
Keywords: checkin-needed
Comment 4•11 years ago
|
||
Keywords: checkin-needed
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla34
You need to log in
before you can comment on or make changes to this bug.
Description
•