Closed Bug 655020 Opened 14 years ago Closed 12 years ago

Intermittent timeout in test_closeOnGC.html

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox6 - ---

People

(Reporter: KaiE, Unassigned)

References

Details

(Keywords: intermittent-failure, regression, Whiteboard: [disabled on windows] fallout from -O3 optimization ?)

3706 ERROR TEST-UNEXPECTED-FAIL | /tests/dom/src/threads/test/test_closeOnGC.html | Test timed out.
This seems to be fallout from gcc 4.5.
Blocks: 590181
Blocks: gcc4.5
No longer blocks: 590181
No longer blocks: gcc4.5
Blocks: 590181
Summary: Intermittent timeout in /tests/dom/src/threads/test/test_closeOnGC.html → Intermittent timeout in test_closeOnGC.html
Blocks: gcc4.5
No longer blocks: 590181
Blocks: 438871
Those two from TraceMonkey are my reason for thinking it's gcc-4.5 related, those being from when TM had gotten the gcc-4.5 build-automation switch, but had not yet merged from mozilla-central and gotten whatever it was that stopped the a11y failures, and apparently also stopped this, until the whatever-it-was was backed out of mozilla-central.
Presumably the "whatever-it-was" from comment 4 is either PGO or -O3 optimization.
Most likely -O3
OS: Windows Server 2003 → Linux
Hardware: All → x86_64
Whiteboard: [orange] → [orange] fallout from -O3 optimization ?
So, can anybody spot when TraceMonkey (comment 11, comment 12, comment 13) merged to mozilla-central, when mozilla-central merged to mozilla-inbound, and when mozilla-central merged to ux?
(In reply to comment #141) > Disabled on Windows in > http://hg.mozilla.org/integration/mozilla-inbound/rev/d6ecab455b57 Merged: http://hg.mozilla.org/mozilla-central/rev/d6ecab455b57
OS: Linux → All
Hardware: x86_64 → All
Whiteboard: [orange] fallout from -O3 optimization ? → [orange][disabled on windows] fallout from -O3 optimization ?
I'm not sure what good the release team can do by tracking this issue. Is this a regression that's expected to get a fix or even needs fixing for Firefox 6?
Nothing to track for 6 here afaict.
tracking-firefox6: + → -
Whiteboard: [orange][disabled on windows] fallout from -O3 optimization ? → [disabled on windows] fallout from -O3 optimization ?
The last 4 were real bustage. The offending patch was backed out.
The test was reenabled in bug 713069 more than a year ago and wasn't starred since then.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.