-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
failed test: parallel/test-tls-no-sslv3.js with shared openssl #618
Comments
When configured with share openssl, use external openssl command and check if it can be executed. Fixes: nodejs#618
When configured with share openssl, use external openssl command and check if it can be executed. Fixes: nodejs#618
When configured with share openssl, use external openssl command and check if it can be executed. Fixes: #618 PR-URL: #762 Reviewed-By: Ben Noordhuis <[email protected]>
Fixed in #762 |
Here's the result from the test after fixing path to openssl binary:
|
@jbergstroem Thanks for your report. This error comes from the change of an error message in openssl-1.0.2 and it is to be fixed with shigeki@72031e6 after upgrading to openssl-1.0.2 . Please wait for a moment until I finish it. |
@shigeki confirmed -- just tried with openssl 1.0.1l. I'm closing since we shouldn't assume 1.0.2 is working until that work is merged. |
The problem is that common.opensslCli will return false instead of a path to the openssl-binary, since it hasn't been built. The simple way is just to check for false before running the test, but it feels like a poor decision since we'd probably want to run the test suite with a shared openssl as much as possible (so the user can verify that their setup is correct).
The text was updated successfully, but these errors were encountered: