./mach jsapi-tests crashes in testBinASTReaderContextECMAScript2
Categories
(Core :: JavaScript Engine, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox77 | --- | fixed |
People
(Reporter: mgaudet, Assigned: arai)
Details
Attachments
(1 file)
Tried running ./mach jsapi-tests
and got the following failure
testBinASTReaderContextECMAScript2
runTestFromPath: entering directory 'jsapi-tests/binast/parser/context/'
Hit MOZ_CRASH(Couldn't open directory) at /home/matthew/unified/js/src/jsapi-tests/testBinASTReader.cpp:183
Comment 1•5 years ago
|
||
Could this be that the test case expect to be running in a given directory, that the mach
command does not respect?
Assignee | ||
Updated•5 years ago
|
Comment 2•5 years ago
|
||
mach
is running it from the wrong directory. The BinAST tests have to run from $SRCDIR/js/src
. It's not good.
Yeah, that's not good. I haven't found a better way to make it work, but if anybody has ideas, I'm interested.
Updated•5 years ago
|
Assignee | ||
Comment 4•5 years ago
|
||
to avoid depending on cwd, one option is to refer env var like TOPSRCDIR
.
for automation, we can specify it in autospider.py
for local run, we could either, abort if it's not specified, or maybe fallback to some common cwds.
Comment 5•5 years ago
|
||
(In reply to David Teller [:Yoric] (please use "needinfo") from comment #3)
Yeah, that's not good. I haven't found a better way to make it work, but if anybody has ideas, I'm interested.
Hmm. I imagine C++ __FILE__
is useless because it's relative?
The code under test here is largely generated C++; what if the code-generator spat the absolute path to the test directory into the C++ code somewhere? Then there could be a function in jsfriendapi.h to get that path.
Assignee | ||
Comment 6•5 years ago
|
||
looks like, we have topsrcdir
macro defined by command line parameter while compiling, that points js/src with absolute path.
I'll use it.
Assignee | ||
Comment 7•5 years ago
|
||
Updated•5 years ago
|
Comment 9•5 years ago
|
||
bugherder |
Description
•