If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

GenerationalGC: Frequent test timeouts running mochitest browser chrome in debug builds

RESOLVED FIXED in mozilla29

Status

()

Core
JavaScript Engine
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: jonco, Assigned: jonco)

Tracking

unspecified
mozilla29
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Assignee)

Description

4 years ago
There are now frequent test timeouts when running the mochitest bc tests, for example:

https://tbpl.mozilla.org/php/getParsedLog.php?id=32526876&tree=Try

These are annoying because they can hide real test failures.

This is caused by the time spent in minor GC.  I've found that taking out the hashtable checking assertions fixes the issue, but I don't want to do this for all builds as I think these are really important to keep.

I've experimented with only running the checks when necessary (i.e. when the relevant tables had entries added) but this didn't totally fix the issue.

My current thought is to also add a configure flag to enable these assertions and only turn them on for shell builds.
The M-bc tests have also been bumping up against memory limits, especially with the Address Sanitizer builds, so there is some pressure to split them up already. I don't know the state of that, though. One of bug 931002, bug 927295, bug 939036, or bug 931340 ought to have more info.
The above bugs are useless. It's bug 819963, which looks like it'll happen before too long, though it's a bit of a mess.
(Assignee)

Comment 3

4 years ago
(In reply to Steve Fink [:sfink] from comment #2)

Unfortunately it's not just that the whole test suite is timing out - individual tests are timing out too.  So we need to do something more that just split the suite up.
(Assignee)

Comment 4

4 years ago
Created attachment 8360458 [details] [diff] [review]
zeal-mode-hashtable-checks

As suggested by Terrence, we can add a new zeal mode to enable these checks.  That way the fuzzers can use them without them slowing down out testing.
Attachment #8360458 - Flags: review?(terrence)
Comment on attachment 8360458 [details] [diff] [review]
zeal-mode-hashtable-checks

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

\o/ r=me
Attachment #8360458 - Flags: review?(terrence) → review+
(Assignee)

Comment 6

4 years ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/dc286d6f6ef8
https://hg.mozilla.org/mozilla-central/rev/dc286d6f6ef8
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla29
(Assignee)

Comment 8

4 years ago
Oh, I broke windows builds (GGC only) with my use of "and" for "&&" in #if directives.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Assignee)

Comment 9

4 years ago
Created attachment 8361805 [details] [diff] [review]
fix-windows-build-errors

Here's a patch to fix that.
Attachment #8361805 - Flags: review?(terrence)
Comment on attachment 8361805 [details] [diff] [review]
fix-windows-build-errors

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

r=me
Attachment #8361805 - Flags: review?(terrence) → review+
(Assignee)

Comment 11

4 years ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/9a84eebfcd41
https://hg.mozilla.org/mozilla-central/rev/9a84eebfcd41
Status: REOPENED → RESOLVED
Last Resolved: 4 years ago4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.