-
-
Notifications
You must be signed in to change notification settings - Fork 6.7k
Test 1700 fails inexplicably in 8.13.0 without the openssl tool present #16926
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
Comments
In these commit some may be safely discarded, leaving:
Possibly the last one may be related if the nghttpx server doesn't like the new test certs. Any details of your build configuration, env? |
I have extracted some information from the build log above. The configure script shows the following:
Few things that seem worth pointing out. I am using GnuTLS. nghttp2 is in version 1.58. In general, software on $PATH has the following versions:
I will try to revert some of the commits above to see if it helps. |
Might be unrelated by I cannot spot openssl on the list of installed software. |
Is this the only test failure you get? Judging by the output it seems curl does not even get the HTTP/1 status line back in test 1700, which would rather indicate some infra problem rather than a curl bug. |
As far as I can tell from the build log, this is the only test failure. However when I excluded 1700, 1701 failed instead. |
@vszakats you seem to be right. From his build log:
|
Oh, this is it! When I add openssl into the build environment, the test start passing. |
I am not sure how I feel about needing two separated crypto packages for the build (gnutls for the linking, openssl for the tests), but it is easy to fix in the package definition. Thank you very much. :) If you think there is nothing else to do, feel free to close this, but maybe some more descriptive error message when openssl is missing would be nice. |
Yeah, we need to improve this so that it is more apparent what happens and what's needed. |
I agree it is not ideal, but this for the moment the best setup we have figured out. 8.13.0 is the first release that generates these certificates on demand instead of using pre-generated certs shipped with the release. |
Reported-by: W. Fixes curl#16926
One mitigation is to fail early with an explicit error if |
I did this
I tried to update my curl package to 8.13.0, however during running the test suite I got the following error:
I have tried bisecting but did not have much luck due to skipping some commit due to tests failing for other reasons.
Topologically first commit is
44341e736a3e2f7a2b25a774be3a9796e81abab9
, and44341e736a3e2f7a2b25a774be3a9796e81abab9~1
does build (and test) fine.I would be happy to provide more information if you need any.
Full build output attached.
sy4ihiiy32ax3mfpyg5z785ak5r4gm-curl-full-8.12.1.drv.gz
I expected the following
I expected the tests to pass.
curl/libcurl version
curl 8.13.0
operating system
Linux host 6.12.20 #1 SMP PREEMPT_DYNAMIC 1 x86_64 GNU/Linux
Distribution: GNU Guix
The text was updated successfully, but these errors were encountered: