Intermittent 472237-1.html | Test timed out

RESOLVED WORKSFORME

Status

()

Core
CSS Parsing and Computation
RESOLVED WORKSFORME
7 years ago
5 years ago

People

(Reporter: mstange, Unassigned)

Tracking

({intermittent-failure})

Trunk
All
Mac OS X
intermittent-failure
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1291213775.1291215035.26098.gz
Rev3 MacOSX Leopard 10.5.8 mozilla-central debug test crashtest on 2010/12/01 06:29:35
s: talos-r3-leopard-020

REFTEST TEST-UNEXPECTED-FAIL | http://localhost:4444/1291214003833/3/crashtests/472237-1.html | timed out waiting for onload to fire
TEST-UNEXPECTED-FAIL | Shutdown | application timed out after 330 seconds with no output
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Tip: It isn't a random orange if it happens every run.

Should be fixed by backout http://hg.mozilla.org/mozilla-central/rev/1b4041e3c177
No longer blocks: 438871, 472237
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Whiteboard: [orange]
(Reporter)

Comment 6

7 years ago
That was a very valuable tip, thanks!

Honestly, somehow I thought it had already happened before my push, but I hadn't realized that that was a different crashtest timeout.
(In reply to comment #6)
> That was a very valuable tip, thanks!
> 
> Honestly, somehow I thought it had already happened before my push, but I
> hadn't realized that that was a different crashtest timeout.

Well the good news is you may have been right all along, this is still showing up after the backout. The bad news is it is still (nearly) permanent orange and I have no clue why at the moment.
Blocks: 438871
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Whiteboard: [orange]
The current state is this:

This problem is causing crashtests on Leopard to hang on shutdown and on debug builds to also timeout during 472237-1.html
We've re-run crashtests on old supposedly good builds and they are failing too. Crashtest runs on the try server are also failing, even when the try pushes were based on day old m-c changesets.
Crashtests seem to have started failing at 5am.
bhearsum tried setting the date back to yesterday on a slave and running manually and was still seeing a hang.
Comment hidden (Treeherder Robot)

Comment 10

7 years ago
The shutdown timeout was happening because of bug 616088.  I filed and fixed bug 616085, so I'm morphing this bug to only cover the test failure.
Summary: Intermittent 472237-1.html | Test timed out followed by shutdown timeout → Intermittent 472237-1.html | Test timed out

Updated

7 years ago
Depends on: 616088
The test timeout didn't happen before the DNS issues and I gather hasn't happened since. Any reason to suspect it is a different issue?

Comment 12

7 years ago
(In reply to comment #11)
> The test timeout didn't happen before the DNS issues and I gather hasn't
> happened since. Any reason to suspect it is a different issue?

Can you explain why the the DNS failure should result in this test timing out?  Cause I sure can't!
It wouldn't surprise me at all if 'localhost' requires waiting for a DNS lookup to complete.  (I know that when we do example.com in mochitest, through the PAC file, we do and wait for a DNS lookup on example.com.)
Depends on: 739506

Updated

6 years ago
No longer depends on: 739506
Status: REOPENED → RESOLVED
Last Resolved: 7 years ago5 years ago
Resolution: --- → WORKSFORME
(Assignee)

Updated

5 years ago
Keywords: intermittent-failure
(Assignee)

Updated

5 years ago
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.