Closed
Bug 619788
Opened 14 years ago
Closed 14 years ago
maemo unittests: disable mochitest-chrome, xpcshell known fail count -> 0
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mozilla, Assigned: mozilla)
Details
Attachments
(1 file)
3.01 KB,
patch
|
jhford
:
review+
mozilla
:
checked-in+
|
Details | Diff | Splinter Review |
I was looking at the Mobile tree on tinderbox and noticed we are running chrome and xpcshell. I think we need to stop running mochitest-chrome as there is work needed to get this fully IPC/e10s compliant. That is a lower priority for me because there will be harness and testcase work. For xpcshell, we have a threshold of acceptable tests. We still have a good number of failures (40), and I would like to lower this threshold to either our current failure number or zero. Lowering it to zero and putting it on the ignore list will allow for us to monitor the status easier while we work on fixing the specific tests which are broken. thoughts? -Joel
Assignee | ||
Comment 1•14 years ago
|
||
Attachment #498217 -
Flags: review?(jhford)
Comment 2•14 years ago
|
||
Comment on attachment 498217 [details] [diff] [review] do the above in configs at some point we should take out the fail count off sets if we end up setting all of them to zero
Attachment #498217 -
Flags: review?(jhford) → review+
Assignee | ||
Comment 3•14 years ago
|
||
(In reply to comment #2) > at some point we should take out the fail count off sets if we end up setting > all of them to zero that was the plan, from day 1 :) it's just taken a little while.
Assignee | ||
Comment 4•14 years ago
|
||
Comment on attachment 498217 [details] [diff] [review] do the above in configs http://hg.mozilla.org/build/buildbot-configs/rev/83b40e84fc2d
Attachment #498217 -
Flags: checked-in+
Assignee | ||
Comment 5•14 years ago
|
||
Should be fixed.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•