You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The test runner for asm.js targets currently always runs them via nodejs, but that name is not universal across distributions- in fact the official name for the Node binary is node. Debian (and presumably Debian derivatives) uses the former name due to a name conflict with another tool.
It would be good to support both via detection at runtime, probably preferring nodejs and trying node if that is not available. In the interest of performance, this should probably be tested only once per run, with a lazy static or similar. Reporting an error if neither is found would also be useful, rather than the current behavior of failing tests due to being unable to invoke the javascript engine.
The text was updated successfully, but these errors were encountered:
Rather than hardcoding the binary name for running asmjs tests, attempt
to detect the name that should be used; either `nodejs` or `node`. Also
add a command-line argument to manually specify what should be used,
suppressing probing.
Fixesrust-lang#34188.
…lexcrichton
compile-test: allow overriding nodejs binary location
Add a command-line argument to manually specify which nodejs binary should be used,
which disables the default search.
Original work done by @tari.
Fixes#34188.
The test runner for asm.js targets currently always runs them via
nodejs
, but that name is not universal across distributions- in fact the official name for the Node binary isnode
. Debian (and presumably Debian derivatives) uses the former name due to a name conflict with another tool.It would be good to support both via detection at runtime, probably preferring
nodejs
and tryingnode
if that is not available. In the interest of performance, this should probably be tested only once per run, with a lazy static or similar. Reporting an error if neither is found would also be useful, rather than the current behavior of failing tests due to being unable to invoke the javascript engine.The text was updated successfully, but these errors were encountered: