-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Use NODE_JS_TEST over NODE_JS in test code #25063
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
Conversation
|
This would be good to land. I pulled this locally into the integrated big endian node emsdk, but after this PR, I still get a bunch of failures in the suite: http://localhost:8010/api/v2/logs/32577/raw_inline e.g. here is true. My ['/mnt/ssd1000/emscripten_buildbot/worker_root/x10dax-linux-mint22/emscripten_x10dax/build/node/nightly-v25.0.0-nightly202507249188563304/bin/node'] The way I set up the big endian node is I have and But it seems that is not enough, but there is some other addition that is needed? Do I need to customize adding |
yes that should be enough. js_engines should be populated from confgi.JS_ENGINES should should default to just NODE_JS_TEST. The |
Emsdk generates
```
import os
emsdk_path = os.path.dirname(os.getenv('EM_CONFIG')).replace('\\', '/')
LLVM_ROOT = emsdk_path + '/llvm/git/build_main_64/bin'
NODE_JS = emsdk_path + '/node/22.16.0_64bit/bin/node'
EMSCRIPTEN_ROOT = emsdk_path + '/emscripten/main'
BINARYEN_ROOT = emsdk_path + '/binaryen/main_64bit_binaryen'
NODE_JS_TEST = ['qemu-s390x', '-L', '/usr/s390x-linux-gnu/', emsdk_path + '/node-big-endian-crosscompile/22.16.0_64bit/bin/node']
```
when activating regular and big endian node. This results in a
non-working Emscripten installation that complains about NODE_JS not
found.
Comment at
#25063 (comment)
suggests that the intent is that if NODE_JS_TEST is populated, it should
go to JS_ENGINES, so make that happen.
See #20573