Frequent Android xpcshell [taskcluster:error] Task timeout after 5400 seconds. Force killing container.
Categories
(Core :: Networking, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr102 | --- | unaffected |
| firefox-esr115 | --- | unaffected |
| firefox115 | --- | unaffected |
| firefox116 | --- | unaffected |
| firefox117 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: kershaw)
References
(Regression)
Details
(Keywords: intermittent-failure, regression, Whiteboard: [necko-triaged] [necko-priority-queue][stockwell disable-recommended])
Attachments
(1 file)
Filed by: csabou [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=421965797&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Bal5dqlyT9iSwmWQebdkRw/runs/0/artifacts/public/logs/live_backing.log
[task 2023-07-08T08:15:37.226Z] 08:15:37 INFO - TEST-SKIP | netwerk/test/unit/test_http3_server.js | took 0ms
[task 2023-07-08T08:15:37.226Z] 08:15:37 INFO - TEST-START | netwerk/test/unit/test_http3_dns_retry.js
[task 2023-07-08T08:15:37.227Z] 08:15:37 INFO - TEST-SKIP | netwerk/test/unit/test_http3_dns_retry.js | took 0ms
[task 2023-07-08T08:15:37.227Z] 08:15:37 INFO - INFO | Result summary:
[task 2023-07-08T08:15:37.227Z] 08:15:37 INFO - INFO | Passed: 403
[task 2023-07-08T08:15:37.227Z] 08:15:37 INFO - INFO | Failed: 0
[task 2023-07-08T08:15:37.227Z] 08:15:37 INFO - INFO | Todo: 1
[task 2023-07-08T08:15:37.227Z] 08:15:37 INFO - INFO | Retried: 32
[task 2023-07-08T08:15:37.227Z] 08:15:37 INFO - SUITE-END | took 852s
[task 2023-07-08T08:15:37.227Z] 08:15:37 INFO - Node moz-http2 server shutting down ...
[task 2023-07-08T08:15:37.227Z] 08:15:37 INFO - Process stdout
[task 2023-07-08T08:15:37.227Z] 08:15:37 INFO - forked process without handler sent: {"error":"","errorStack":""}
[task 2023-07-08T08:15:37.228Z] 08:15:37 INFO - error: Command failed: /builds/worker/fetches/android-sdk-linux/platform-tools/adb reverse tcp:35914 tcp:35914
[task 2023-07-08T08:15:37.228Z] 08:15:37 INFO - adb: error: cannot bind listener: Address already in use
[task 2023-07-08T08:15:37.228Z] 08:15:37 INFO - error: Command failed: /builds/worker/fetches/android-sdk-linux/platform-tools/adb reverse tcp:46547 tcp:46547
[task 2023-07-08T08:15:37.228Z] 08:15:37 INFO - adb: error: cannot bind listener: Address already in use
[taskcluster:error] Task timeout after 5400 seconds. Force killing container.
[taskcluster 2023-07-08 09:29:21.069Z] === Task Finished ===
[taskcluster 2023-07-08 09:29:21.070Z] Unsuccessful task run with exit code: -1 completed in 5400.941 seconds
Comment 1•2 years ago
|
||
Comment 2•2 years ago
|
||
This reminds me of bug 1824708, but I don't know if it is actually related.
Comment 3•2 years ago
|
||
Set release status flags based on info from the regressing bug 1842167
:standard8, since you are the author of the regressor, bug 1842167, could you take a look?
For more information, please visit BugBot documentation.
Comment 4•2 years ago
|
||
The interesting bits are these:
INFO - error: Command failed: /builds/worker/fetches/android-sdk-linux/platform-tools/adb reverse tcp:35914 tcp:35914
adb: error: cannot bind listener: Address already in use
That seems to be new and shows up in the affected builds. I tried hunting down where the reverse happens, but came up with multiple different places.
The change from my bug is effectively upgrading from Node 12 to Node 16. So maybe there's some different characteristics for shutdown?
I think these are all triggered by the netwerk/test/unit/ tests, so maybe there's something in there that's causing it.
Kershaw, would you happen to have any ideas here?
| Comment hidden (Intermittent Failures Robot) |
| Assignee | ||
Comment 6•2 years ago
|
||
(In reply to Mark Banner (:standard8) from comment #4)
The interesting bits are these:
INFO - error: Command failed: /builds/worker/fetches/android-sdk-linux/platform-tools/adb reverse tcp:35914 tcp:35914 adb: error: cannot bind listener: Address already in useThat seems to be new and shows up in the affected builds. I tried hunting down where the
reversehappens, but came up with multiple different places.The change from my bug is effectively upgrading from Node 12 to Node 16. So maybe there's some different characteristics for shutdown?
I think these are all triggered by the
netwerk/test/unit/tests, so maybe there's something in there that's causing it.Kershaw, would you happen to have any ideas here?
I think it's likely that the error is from this line.
I'll try to debug this and see if I can find a solution for this.
| Comment hidden (Intermittent Failures Robot) |
| Assignee | ||
Comment 8•2 years ago
|
||
Updated•2 years ago
|
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Comment 9•2 years ago
|
||
Comment 10•2 years ago
|
||
Comment 11•2 years ago
|
||
| bugherder | ||
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Description
•