Linux tracemonkey moz2-linux-slave09 dep unit test is stuck

RESOLVED FIXED

Status

Release Engineering
General
P1
critical
RESOLVED FIXED
9 years ago
4 years ago

People

(Reporter: gal, Assigned: nthomas)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

9 years ago
TinderboxPrint: TUnit<br/>442/0
Couldn't find profile location
NEXT ERROR Error: no display specified

Didn't come back after the NAS firmware upgrade or whatever happened yesterday night.

We can't merge into MC until this is fixed, so this is blocking b2 IMO.

Comment 1

9 years ago
Seems like tinderbox was restarted incorrectly.
Assignee: build → server-ops
Component: Tinderbox Configuration → Server Operations: Tinderbox Maintenance
QA Contact: ccooper → mrz
Looking.
Assignee: server-ops → bhearsum
Status: NEW → ASSIGNED
Priority: -- → P1
I think that metacity hadn't been started when it was restarted last night. Not sure. Should be OK now though.
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
(Reporter)

Comment 4

9 years ago
http://tinderbox.mozilla.org/showlog.cgi?log=TraceMonkey/1226605735.1226605735.14228.gz

Linux tracemonkey moz2-linux-slave09 dep unit test
Started 11:48, still building..
2 hours, 33 minutes elapsed

The box seems to be stuck still (the test usually takes less than an hour). We can't ship TM for b2 if our test coverage is broken.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Assignee)

Comment 5

9 years ago
Looking
Assignee: bhearsum → nthomas
Component: Server Operations: Tinderbox Maintenance → Release Engineering: Maintenance
QA Contact: mrz → release
(Assignee)

Comment 6

9 years ago
The build that started at 11:48 did finish, but at 13:35 when tinderbox.m.o was having difficulties. Probably it will have dropped the build-end mail and given us the perma-yellow box. The results were 
  TUnit: 442/0
  reftest: 2310/0/84
  crashtest: 774/0/2
  mochitest: FAIL (timeout)
  chrome: 978/0/28
  browser: 931/0/5
All green except the mochitest, the log for which ends:
*** 28480 INFO Running /tests/dom/src/threads/tests/test_threadErrors.html...
*** 28482 INFO Running /tests/dom/src/threads/tests/test_threadTimeouts.html...
*** 28483 INFO TEST-PASS | /tests/dom/src/threads/tests/test_threadTimeouts.html | undefined
*** 28484 INFO TEST-PASS | /tests/dom/src/threads/tests/test_threadTimeouts.html | undefined
*** 28485 INFO TEST-PASS | /tests/dom/src/threads/tests/test_threadTimeouts.html | undefined
*** 28487 INFO Running /tests/dom/src/threads/tests/test_xhr.html...
*** 28488 ERROR TEST-UNEXPECTED-FAIL | /tests/dom/src/threads/tests/test_xhr.html | Test timed out.
command timed out: 2400 seconds without output, killing pid 17715

This timeout should be shorter so I'll fix that up.

The run that started at 13:35 just completed and is green across the board.
Status: REOPENED → RESOLVED
Last Resolved: 9 years ago9 years ago
Resolution: --- → FIXED
(Assignee)

Comment 7

9 years ago
Both the builds in comment #6 were from rev 5804f5597d3d
(Assignee)

Comment 8

9 years ago
Created attachment 348075 [details] [diff] [review]
Correct timeouts, and add xpcshell.exe kill

Lukas, I made these changes on the tracemonkey master. Just syncing the timeouts to what we use on mozilla-central, and adding the xpcshell killage.
(Reporter)

Comment 9

9 years ago
Looks good. The column went green. Thanks.

Updated

9 years ago
Component: Release Engineering: Maintenance → Release Engineering
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.