Re: Strange failures of Emscripten's tests

[Alon Zakai]

We don't run tests on our CI using the SpiderMonkey shell (but we do test
Firefox in the browser suite), so perhaps we need to add something in
src/shell.js for it.

Our CI shell tests mostly run in node, with a few using d8 when we test
very new wasm features not yet in node.

The current status of the tests can be seen on github where we run CI,

https://github.com/emscripten-core/emscripten/commits/master

Each commit has a green check or a red x, and clicking on those gets you to
links to see the detailed results.


On Sun, May 31, 2020 at 7:10 AM Qwerty Uiop  wrote:

> Hi,
>
> I've been trying to run Emscripten's tests locally and I've got strange
> failures.
>
> E.g. when I run
> python tests/runner.py test_unistd_io
> I get
> ...
> AssertionError: JS subprocess failed (/home/brd/soft/SpiderMonkeyShell-
> nightly-2020-05-30/js -w /tmp/emscripten_test/src.cpp.o.js): 1.  Output:
> Assertion failed: undefined
> Assertion failed: undefined
> exception thrown: RuntimeError: abort(Assertion failed: undefined) at
> jsStackTrace@/tmp/emscripten_test/src.cpp.o.js:7402:17
> ...
>
> The line 7402 of src.cpp.o.js is the first line of the function
> jsStackTrace:
> var err = new Error();
> So it looks like Error itself is undefined.
> Of course, when I run SpiderMonkey on a simple js file containing just
> that line, it works fine.
>
> I'm using the latest master revisions of Emscripten, Fastcomp and Binaryen
> as of Friday, May 29.
>
> I have the impression that something is wrong with my setup but can't
> figure out where the problem is exactly.
> Could anyone give me a clue?
>
> Also, could anyone point me to the official build server where I might see
> the current status of the tests?
>
> --
> You received this message because you are subscribed to the Google Groups
> "emscripten-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to emscripten-discuss+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/emscripten-discuss/6bccd969-e9fa-4b4e-a505-6a69c0d492ba%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to emscripten-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/emscripten-discuss/CAEX4NpQkLSSyvM495BwnYfrvx3KDG2nz7Q%3DPrezRGtokFb5ywg%40mail.gmail.com.

Strange failures of Emscripten's tests

[Qwerty Uiop]

Hi,

I've been trying to run Emscripten's tests locally and I've got strange 
failures.

E.g. when I run 
python tests/runner.py test_unistd_io
I get 
...
AssertionError: JS subprocess failed (/home/brd/soft/SpiderMonkeyShell-
nightly-2020-05-30/js -w /tmp/emscripten_test/src.cpp.o.js): 1.  Output:
Assertion failed: undefined
Assertion failed: undefined
exception thrown: RuntimeError: abort(Assertion failed: undefined) at 
jsStackTrace@/tmp/emscripten_test/src.cpp.o.js:7402:17
...

The line 7402 of src.cpp.o.js is the first line of the function jsStackTrace
:
var err = new Error();
So it looks like Error itself is undefined.
Of course, when I run SpiderMonkey on a simple js file containing just that 
line, it works fine.

I'm using the latest master revisions of Emscripten, Fastcomp and Binaryen 
as of Friday, May 29.

I have the impression that something is wrong with my setup but can't 
figure out where the problem is exactly.
Could anyone give me a clue?

Also, could anyone point me to the official build server where I might see 
the current status of the tests?

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to emscripten-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/emscripten-discuss/6bccd969-e9fa-4b4e-a505-6a69c0d492ba%40googlegroups.com.