autopkgtests sometimes hang on armhf
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| firefox (Ubuntu) |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
This has been most recently observed with firefox 70.0.1+
I cannot reproduce the problem consistently, but I've observed it at least once in a test environment (focal/armhf lxd container running on a bionic/arm64 cloud instance), and it has happened quite a few times lately on the ubuntu autopkgtest infrastructure.
The html5test hangs indefinitely, and only times out after more than 5 hours (=20000 seconds, which is the test timeout hardcoded in the infrastructure).
When I reproduced the hang, this was the list of (relevant) running processes:
root 5554 5545 0 05:55 ? 00:00:02 /usr/bin/python3 /tmp/autopkgtes
root 5561 5554 0 05:55 ? 00:00:00 geckodriver --port 42963
root 5569 5561 0 05:55 ? 00:00:17 /usr/lib/
root 5611 5569 0 05:55 ? 00:00:05 /usr/lib/
root 5632 5569 0 05:55 ? 00:00:14 /usr/lib/
root 5676 5569 0 05:55 ? 00:00:00 /usr/lib/
I straced them all and the geckodriver process is the one that appeared blocked:
root@
strace: Process 5561 attached
futex(
Here is the test output when it hangs:
autopkgtest [07:14:56]: test firefox-version: - - - - - - - - - - results - - - - - - - - - -
firefox-version PASS
autopkgtest [07:14:59]: test html5test: preparing testbed
Reading package lists...
Building dependency tree...
Reading state information...
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up autopkgtest-satdep (0) ...
(Reading database ... 59615 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [07:15:29]: test html5test: [------
127.0.0.1 - - [22/Nov/2019 07:15:45] "GET / HTTP/1.1" 200 -
127.0.0.1 - - [22/Nov/2019 07:15:47] "GET /css/main.css HTTP/1.1" 200 -
127.0.0.1 - - [22/Nov/2019 07:15:47] "GET /scripts/base.js HTTP/1.1" 200 -
127.0.0.1 - - [22/Nov/2019 07:15:47] "GET /scripts/
127.0.0.1 - - [22/Nov/2019 07:15:47] "GET /scripts/8/data.js HTTP/1.1" 200 -
127.0.0.1 - - [22/Nov/2019 07:15:52] "GET /images/html5.png HTTP/1.1" 200 -
127.0.0.1 - - [22/Nov/2019 07:15:53] "GET /images/
127.0.0.1 - - [22/Nov/2019 07:15:53] "GET /fonts/
127.0.0.1 - - [22/Nov/2019 07:15:53] "GET /fonts/
127.0.0.1 - - [22/Nov/2019 07:15:53] "GET /assets/
127.0.0.1 - - [22/Nov/2019 07:15:53] "GET /assets/
127.0.0.1 - - [22/Nov/2019 07:15:53] "GET /assets/
127.0.0.1 - - [22/Nov/2019 07:15:53] "GET /assets/
127.0.0.1 - - [22/Nov/2019 07:15:53] "GET /images/
127.0.0.1 - - [22/Nov/2019 07:15:53] "GET /images/
Related branches
| Olivier Tilloy (osomon) wrote | #1 |
| Changed in firefox (Ubuntu): | |
| assignee: | nobody → Olivier Tilloy (osomon) |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| Olivier Tilloy (osomon) wrote | #2 |
| Olivier Tilloy (osomon) wrote | #3 |
| Launchpad Janitor (janitor) wrote | #4 |
| Changed in firefox (Ubuntu): | |
| status: | Triaged → Fix Released |
| Olivier Tilloy (osomon) wrote | #5 |
| Changed in firefox (Ubuntu): | |
| status: | Fix Released → Triaged |
| Changed in firefox (Ubuntu): | |
| assignee: | Olivier Tilloy (osomon) → nobody |
If the cause of the hang cannot easily be determined, we should at least make sure that the test doesn't hang for 5+ hours, until it times out (i.e. we need a lower timeout, 5 minutes is probably fine).