Open
Bug 1412817
Opened 8 years ago
Updated 3 years ago
tests are failing in mochitest but there is no TEST-UNEXPECTED-FAIL and it isn't obvious where the failures is
Categories
(Testing :: Mochitest, defect)
Testing
Mochitest
Tracking
(Not tracked)
NEW
People
(Reporter: jmaher, Unassigned)
Details
I have two log files:
https://treeherder.mozilla.org/logviewer.html#?repo=autoland&job_id=139597684
https://treeherder.mozilla.org/logviewer.html#?repo=autoland&job_id=139606148
search for 'INFO Failed: 1', and you will see the failure while running the /tests/dom/performance/tests/ directory.
Unfortunately I cannot figure out where the failure is coming from- and the sheriffs are randomly star'ing this.
Reporter | ||
Comment 1•8 years ago
|
||
:ahal, could you take a look at the logs above and see if you can find the error?
Flags: needinfo?(ahalberstadt)
Comment 2•8 years ago
|
||
Could it be those memory leaks? Didn't the leak thresholds recently get dropped down to 0? That might explain why there are more frequent intermittents, though doesn't explain why it wouldn't be highlighted by treeherder.
Flags: needinfo?(ahalberstadt)
Reporter | ||
Comment 3•8 years ago
|
||
yeah, that is probably it- I am not aware of the threshold changing- is there a bug with data on that?
Comment 4•8 years ago
|
||
Hm, there was bug 1409075, though that didn't bump it down to 0:
https://hg.mozilla.org/mozilla-central/diff/438ff19208f4/testing/mochitest/mochitest_options.py
I must have been thinking about bug 1411259, but that hasn't landed yet (and looks to be non-Windows only). So maybe this isn't due to the leaks. And if it was a leak, I think it should be outputting TEST-UNEXPECTED-FAIL somewhere, which it isn't. So something is wrong here either way.
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•