Perma [tier2] Windows 32-bit spidermonkey plain js\src\jit-test\tests\regexp\huge-02.js | Unknown (code 3221225725, args "") [0.2 s]
Categories
(Core :: JavaScript Engine, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox76 | --- | unaffected |
firefox77 | --- | unaffected |
firefox78 | --- | unaffected |
firefox79 | --- | fixed |
People
(Reporter: aryx, Assigned: iain)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
Log: https://treeherder.mozilla.org/logviewer.html#?job_id=305187807&repo=mozilla-central
TEST-UNEXPECTED-FAIL | js\src\jit-test\tests\regexp\huge-02.js | Unknown (code 3221225725, args "") [0.2 s]
42691 TEST-UNEXPECTED-FAIL | js\src\jit-test\tests\regexp\huge-02.js | Unknown (code 3221225725, args "--ion-eager --ion-offthread-compile=off --more-compartments") [0.2 s]
42702 TEST-UNEXPECTED-FAIL | js\src\jit-test\tests\regexp\huge-02.js | Unknown (code 3221225725, args "--ion-eager --ion-offthread-compile=off --ion-check-range-analysis --ion-extra-checks --no-sse3 --no-threads") [0.2 s]
42713 TEST-UNEXPECTED-FAIL | js\src\jit-test\tests\regexp\huge-02.js | Unknown (code 3221225725, args "--baseline-eager") [0.1 s]
42724 TEST-UNEXPECTED-FAIL | js\src\jit-test\tests\regexp\huge-02.js | Unknown (code 3221225725, args "--no-blinterp --no-baseline --no-ion --more-compartments") [0.1 s]
42735 TEST-UNEXPECTED-FAIL | js\src\jit-test\tests\regexp\huge-02.js | Unknown (code 3221225725, args "--blinterp-eager") [0.1 s]
![]() |
Reporter | |
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
This is kind of baffling. Looking into it.
Updated•5 years ago
|
Comment 2•5 years ago
|
||
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Comment 5•5 years ago
|
||
Slow progress, since I don't have access to a win32 machine and have to run tests on try.
I've narrowed the regexp/huge-02.js
failures down to this changeset. I'm still not quite sure how moving some files around managed to break one and only one platform. Looking into it more today.
The other failures (in wasm/simd) appear to be unrelated.
Comment 6•5 years ago
|
||
Thank you for the update!
Updated•5 years ago
|
Assignee | ||
Comment 7•5 years ago
|
||
Update: This is some sort of unified build problem. When the changeset moved files around, the contents of the UNIFIED_SOURCES chunks changed. In particular, it looks like irregexp/imported/regexp-compiler.cc
does not play nicely with at least one of the following files:
imported/regexp-ast.cc
imported/regexp-bytecode-generator.cc
imported/regexp-bytecode-peephole.cc
imported/regexp-bytecodes.cc
imported/regexp-compiler-tonode.cc
Pulling regexp-compiler.cc
out of UNIFIED_SOURCES fixes the problem, but I'm going to run a couple more tests before landing that change to see if I can figure out what's going on, in case there's a real underlying problem. If nothing turns up, I'll land the simple fix.
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Comment 9•5 years ago
|
||
After landing a patch to reorganize the directory structure of our irregexp import, one particular testcase (regexp/huge-02.js
) started failing on Windows 32-bit. It turns out to be a unified build problem: moving around files caused the unified chunks to be allocated slightly differently. After some experimentation, I determined that pulling regexp-compiler.cc
out of the unified build made the problem go away. It looks like it does not play nicely with regexp-compiler-tonode.cc
. I don't have easy access to a win32 machine to dig deeper, so I'm landing the easy patch. If there's a real underlying issue, we can fix it when it shows up on a platform that's easier to debug.
Comment 10•5 years ago
|
||
Comment 11•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Updated•5 years ago
|
Description
•