Closed
Bug 1865592
Opened 2 years ago
Closed 2 years ago
`./mach ide vscode` fails with `Exception: Process executed with non-0 exit code None`
Categories
(Firefox Build System :: Mach Core, defect)
Tracking
(firefox-esr115 unaffected, firefox120 wontfix, firefox121 wontfix, firefox122 fixed)
RESOLVED
FIXED
122 Branch
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox120 | --- | wontfix |
| firefox121 | --- | wontfix |
| firefox122 | --- | fixed |
People
(Reporter: yannis, Assigned: yannis)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
See bug 1814525 comment 15 and bug 1814525 comment 17. ./mach ide vscode fails with Exception: Process executed with non-0 exit code None on my Windows 11 laptop after the patch from bug 1845125. I put extra details and suggestions for code change in my comments from bug 1814525, but I have a more minimalist patch that is enough to fix the issue on my laptop.
| Assignee | ||
Comment 1•2 years ago
|
||
In ProcessHandlerMixin.wait, if the ProcessReader thread is successfully
joined during the last second of timeout, we currently return None. This
can make us return None when the process has already exited. Instead, we
should check if joining was successful, and proceed to normal
Process.wait if it was.
Updated•2 years ago
|
Assignee: nobody → yjuglaret
Status: NEW → ASSIGNED
Updated•2 years ago
|
Severity: -- → S3
Pushed by yjuglaret@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ab3b36e651d9
Proceed to Process.wait if ProcessReader thread is successfully joined. r=firefox-build-system-reviewers,sergesanspaille
Comment 3•2 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox122:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 122 Branch
Comment 4•2 years ago
|
||
Set release status flags based on info from the regressing bug 1845125
status-firefox120:
--- → affected
status-firefox121:
--- → affected
status-firefox-esr115:
--- → unaffected
Updated•2 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•