| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
@danbev build started: https://ci.nodejs.org/blue/organizations/jenkins/node-test-pull-request-lite-pipeline/detail/node-test-pull-request-lite-pipeline/1496/pipeline |
Sorry, something went wrong.
Sorry, something went wrong.
|
This would make the errors different now right? Before it's ERR_NO_CRYPTO, now it's the module not found error? Also, if just to work around the cache generator - you can just push to the cannotUseCache array in lib/internal/bootstrap/cache.js when process.versions.openssl is falsy, similar to how Intl, trace events and inspector gets skipped - although come to think of it, don't we have no crypto jobs in the CI? @refack |
Sorry, something went wrong.
I'm not sure, if there are no existing test for those error messages then that might be an issue. All test pass locally for me using --without-ssl (if I also include #24096 but that is a different failure than this one).
I was thinking that we exclude the crypto object files when configured without-ssl and thought it made sense to also exclude these, but my main goal here is to get the testsuite to pass with --without-ssl so I'll take a look cannotUseCache. Thanks |
Sorry, something went wrong.
No. We only have --without-intl and --shared-openssl, but we can do have CONFIG_FLAGS so lets see: |
Sorry, something went wrong.
I'm trying to figure out how to make this more maintainable 🤔 ... Maybe have a blacklist instead of a whitelist (like V8 does for no-intl - Lines 1892 to 1893 in 7e1b178 Or even better (could be in a later PR) parsed the sources and dynamically filter those out in js2c.py. |
Sorry, something went wrong.
This commit adds JavaScript modules that depend on crypto to the cannotUseCache array. This is to avoid having them compiled when node has been configured --without-ssl which currently fails.
Sorry, something went wrong.
This commit adds JavaScript modules that depend on crypto to the cannotUseCache array. This is to avoid having them compiled when node has been configured --without-ssl which currently fails. PR-URL: nodejs#24100 Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com>
This commit adds JavaScript modules that depend on crypto to the cannotUseCache array. This is to avoid having them compiled when node has been configured --without-ssl which currently fails. PR-URL: #24100 Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com>
This commit adds JavaScript modules that depend on crypto to the cannotUseCache array. This is to avoid having them compiled when node has been configured --without-ssl which currently fails. PR-URL: nodejs#24100 Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com>
This commit adds JavaScript modules that depend on crypto to the cannotUseCache array. This is to avoid having them compiled when node has been configured --without-ssl which currently fails. PR-URL: #24100 Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com>
This commit adds JavaScript modules that depend on crypto to the cannotUseCache array. This is to avoid having them compiled when node has been configured --without-ssl which currently fails. PR-URL: #24100 Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com>
| Back | FazBrowse Home | New Git URL |
This commit adds JavaScript modules that depend on crypto to the cannotUseCache array. This is to avoid having them compiled when node has been configured --without-ssl which currently fails.
With this change the complete testsuite passes again when configured --without-ssl.