Closed
Bug 1504353
Opened 7 years ago
Closed 6 years ago
short lived release task failed with exit code: 137
Categories
(Taskcluster :: Workers, defect)
Taskcluster
Workers
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: jlund, Unassigned)
References
Details
https://taskcluster-artifacts.net/ar6QtOrGSn-X0RSDh7rHiw/0/public/logs/live_backing.log
The task ends abruptly (at least it seems) and does not automatically retry. This requires Releng to force a manual rerun. At a guess, I would assume the worker instance or container is killed and the task ends suddenly. Should these cases result in an automatic retry? Is there an underlining issue that could be fixed?
2018-10-25 19:26:28,434 - INFO - AV-scanning /tmp/tmpdacm89yz/from ...
[taskcluster 2018-10-25 19:26:36.721Z] === Task Finished ===
[taskcluster 2018-10-25 19:26:36.722Z] Artifact "public/build/dsb/target-64.0b3.partial.mar" not found at "/home/worker/artifacts/target-64.0b3.partial.mar"
[taskcluster 2018-10-25 19:26:36.724Z] Artifact "public/build/dsb/manifest.json" not found at "/home/worker/artifacts/manifest.json"
[taskcluster 2018-10-25 19:26:36.725Z] Artifact "public/build/dsb/target-64.0b2.partial.mar" not found at "/home/worker/artifacts/target-64.0b2.partial.mar"
[taskcluster 2018-10-25 19:26:36.726Z] Artifact "public/build/dsb/target-64.0b1.partial.mar" not found at "/home/worker/artifacts/target-64.0b1.partial.mar"
[taskcluster 2018-10-25 19:26:37.584Z] Unsuccessful task run with exit code: 137 completed in 44.743 seconds
Reporter | ||
Comment 1•7 years ago
|
||
hit this with Sipq5wstTP2zZpu5tqVjCw too in b7
Reporter | ||
Comment 2•7 years ago
|
||
another beta Z0l8xFrrRRGyXhgRA9z_Eg
Comment 3•7 years ago
|
||
I wonder if these are OOMs?
Assignee | ||
Updated•7 years ago
|
Component: Docker-Worker → Workers
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•