Closed
Bug 1727740
Opened 3 years ago
Closed 3 years ago
Permanent smoosh subprocess.CalledProcessError: Command '['/builds/worker/checkouts/gecko/mach', 'build']' returned non-zero exit status 2.
Categories
(Core :: JavaScript Engine, defect, P5)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
93 Branch
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox-esr91 | --- | unaffected |
firefox91 | --- | unaffected |
firefox92 | --- | unaffected |
firefox93 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: arai)
References
(Regression)
Details
(Keywords: intermittent-failure, regression)
Attachments
(1 file)
Filed by: archaeopteryx [at] coole-files.de
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=349447074&repo=mozilla-central
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/SLKaWTFzTHyXx5ZGNFZGrw/runs/0/artifacts/public/logs/live_backing.log
[smoosh 0.1.0] thread 'main' panicked at 'Opcodes.h is out of sync. It's possible that the bytecode generated by jsparagus is based on older opcodes. Please run update_stencil.py in jsparagus. You can disable this check by setting JS_SMOOSH_DISABLE_OPCODE_CHECK environment variable.', js/src/frontend/smoosh/build.rs:5:9
Updated•3 years ago
|
status-firefox91:
--- → unaffected
status-firefox92:
--- → unaffected
status-firefox93:
--- → affected
status-firefox-esr78:
--- → unaffected
status-firefox-esr91:
--- → unaffected
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Comment 2•3 years ago
|
||
handled in https://github.com/mozilla-spidermonkey/jsparagus/pull/644
will be vendored here
Assignee: nobody → arai.unmht
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•3 years ago
|
||
Pushed by arai_a@mac.com:
https://hg.mozilla.org/integration/autoland/rev/8d8e688ab900
Bump jsparagus for bug 1726533. r=nbp
Comment 5•3 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 93 Branch
Updated•3 years ago
|
Has Regression Range: --- → yes
You need to log in
before you can comment on or make changes to this bug.
Description
•