New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exception: 'run_command unexpected stderr' when running wasm2js tests with nodejs-14.5.0 #2970
Comments
For now, I'm using the patch below as a work-around: diff -up binaryen-version_95/scripts/test/wasm2js.py.node binaryen-version_95/scripts/test/wasm2js.py
--- binaryen-version_95/scripts/test/wasm2js.py.node 2020-07-21 06:04:33.000000000 +0200
+++ binaryen-version_95/scripts/test/wasm2js.py 2020-07-21 13:43:50.093293525 +0200
@@ -80,7 +80,7 @@ def test_wasm2js_output():
# `spectest` and `env` modules in our tests.
if shared.NODEJS:
loader = os.path.join(shared.options.binaryen_root, 'scripts', 'test', 'node-esm-loader.mjs')
- node = [shared.NODEJS, '--experimental-modules', '--loader', loader]
+ node = [shared.NODEJS, '--experimental-modules', '--no-warnings', '--loader', loader]
cmd = node[:]
cmd.append('a.2asm.mjs')
out = support.run_command(cmd) |
@rathann Interesting, looks like a new node warning then. I think that diff looks good - please open a PR with that, thanks! |
rathann
added a commit
to rathann/binaryen
that referenced
this issue
Jul 21, 2020
Fixes issue WebAssembly#2970 Exception: 'run_command unexpected stderr' when running wasm2js tests with nodejs-14.5.0
kripken
pushed a commit
that referenced
this issue
Jul 22, 2020
Fixes issue #2970 Avoids "Exception: 'run_command unexpected stderr'" when running wasm2js tests with nodejs-14.5.0+, which is due to extra warnings from that node: $ cd out/test/ $ /usr/bin/node --experimental-modules --loader /builddir/build/BUILD/binaryen-version_95/scripts/test/node-esm-loader.mjs a.2asm.mjs (node:187299) ExperimentalWarning: --experimental-loader is an experimental feature. This feature could change at any time (Use `node --trace-warnings ...` to show where the warning was created)
Fixed by that PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is with nodejs-14.5.0.
Indeed, running the above command directly gives an extra line of output:
The text was updated successfully, but these errors were encountered: