Closed
Bug 1868250
Opened 2 years ago
Closed 2 years ago
runxpcshelltests can dead-hang when http2 server doesn't terminate as expected
Categories
(Testing :: XPCShell Harness, defect)
Testing
XPCShell Harness
Tracking
(firefox122 fixed)
RESOLVED
FIXED
122 Branch
| Tracking | Status | |
|---|---|---|
| firefox122 | --- | fixed |
People
(Reporter: glandium, Assigned: glandium)
Details
Attachments
(1 file)
runxpcshelltests.py has the same problem as was found in mozserve/servers.py.
See https://phabricator.services.mozilla.com/D195207 for details.
| Assignee | ||
Comment 1•2 years ago
|
||
When the http2 server prints a bunch of stuff and dies, the loop doesn't
actually have the time to read multiple lines before poll returns
something, breaking the loop... leaving the log without possibly vital
information.
Unfortunately, since killing the process in stop can also lead to
the threads being blocked on readline (see bug 1863675), we also need to
stop joining the threads. If the process terminates normally, the loop
will break itself when the pipe returns nothing, and the threads will
exit on their own.
Pushed by mh@glandium.org:
https://hg.mozilla.org/integration/autoland/rev/fed4b5c2701f
Don't stop reading from the pipe when the process is dead. r=releng-reviewers,ahal
Comment 3•2 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox122:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 122 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•