Closed
Bug 1155554
Opened 10 years ago
Closed 9 years ago
A job is marked as failed whereas nothing failed
Categories
(Taskcluster :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: julienw, Unassigned)
Details
See: https://treeherder.mozilla.org/logviewer.html#?job_id=864212&repo=gaia
When looking at the raw log, we can see it was successful; yet it's displayed as failed.
Moreover we can't see the log in the logviewer and have to look to the raw log.
Comment 1•10 years ago
|
||
(In reply to Julien Wajsberg [:julienw] from comment #0)
> When looking at the raw log, we can see it was successful; yet it's
> displayed as failed.
This is an issue with Taskcluster or the harness.
> Moreover we can't see the log in the logviewer and have to look to the raw
> log.
This is bug 1147958 (taskcluster).
Component: Treeherder: Log Viewer → TaskCluster
Product: Tree Management → Testing
Version: --- → Trunk
The bottom of the raw lag shows the following, for whatever it's worth...
TEST-END | null | [emergency-call-test/unit/ice_contacts_test.js] ICE contacts bar Should create correct DOM Tapping a contact dials them took 4 ms
*** UTM:SVC TimerManager:notify - notified @mozilla.org/b2g/webapps-update-timer;1
*** UTM:SVC TimerManager:notify - notified @mozilla.org/addons/integration;1
*** UTM:SVC TimerManager:notify - notified @mozilla.org/extensions/blocklist;1
*** UTM:SVC TimerManager:notify - notified timerID: user-agent-updates-timer
*** UTM:SVC TimerManager:registerTimer - id: user-agent-updates-timer
[taskcluster] Task timeout after 1800 seconds. Force killing container.
[taskcluster] Unsuccessful task run with exit code: -1 completed in 1800.977
seconds
Updated•10 years ago
|
Component: TaskCluster → General
Product: Testing → Taskcluster
Version: Trunk → unspecified
Comment 3•9 years ago
|
||
The log in comment 2 indicates this was a task timeout, and the task log no longer exists at the link indicated, so closing.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•