-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
test-esm-addon.mjs fails when building in debug mode #16155
Comments
Related, or at least not-unrelated: |
A less-than-fully-satisfying-but-perhaps-effective fix may be to create a wrapper for that checks for the location of The wrapper could also fix the CI issue linked above in that it could skip the test if it can't find the |
Cross-ref: #15445 (comment) |
Proposed fix in #16174 |
Move test-esm-addons to test/addons/hello-world-esm. Test should now work properly on CI machines where `addons` are not always built at the expected relative path from the es-modules tests. Test should now work in Debug builds. Fixes: nodejs#16155
Move test-esm-addons to test/addons/hello-world-esm. Test should now work properly on CI machines where `addons` are not always built at the expected relative path from the es-modules tests. Test should now work in Debug builds. PR-URL: nodejs/node#16174 Fixes: nodejs/node#16155 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Daniel Bevenius <[email protected]> Reviewed-By: Refael Ackermann <[email protected]>
Move test-esm-addons to test/addons/hello-world-esm. Test should now work properly on CI machines where `addons` are not always built at the expected relative path from the es-modules tests. Test should now work in Debug builds. PR-URL: #16174 Fixes: #16155 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Daniel Bevenius <[email protected]> Reviewed-By: Refael Ackermann <[email protected]>
When building with
$ ./configure --debug && make -j8 test
the the following error is reported:The addon tests use
${common.buildType}
to determine the buildType, but it seems that only a string literal is allowed for the import so I'm not sure about a proper way to fix this.The text was updated successfully, but these errors were encountered: