Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: [RELEASE] curl 7.85.0
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Dennis Clarke via curl-library <curl-library_at_lists.haxx.se>
Date: Wed, 7 Sep 2022 17:19:36 -0400
On 9/7/22 00:10, Dan Fandrich via curl-library wrote:
> On Tue, Sep 06, 2022 at 11:57:24PM -0400, Dennis Clarke via curl-library
> wrote:
>> TESTFAIL: These test cases failed: 831 834 877 880 933 936 2023 2024 2026
>> 2027
>>
>> So not sure how to proceed. In the past I was generally able to get a
>> fantastic clean results from curl.
>>
>> So then ... how to proceed here ?
>
> If you run the tests using the -p and/or -v options, you'll get much
> more detailed information about why each test is failing.
This sort of thing is not very helpful at all :
.
.
.
test 0830...OK (663 out of 1512, remaining: 06:00, took 0.111s,
duration: 04:41)
test 0831...
831: protocol FAILED!
There was no content at all in the file log/server.input.
Server glitch? Total curl failure? Returned: 1
test 0833...OK (666 out of 1512, remaining: 05:58, took 0.119s,
duration: 04:42)
test 0834...
834: protocol FAILED!
There was no content at all in the file log/server.input.
Server glitch? Total curl failure? Returned: 1
test 0837...OK (669 out of 1512, remaining: 05:55, took 0.114s,
duration: 04:42)
.
.
.
So I am guessing that there is a way for me to re-run test 831 in
verbose detail.
Date: Wed, 7 Sep 2022 17:19:36 -0400
On 9/7/22 00:10, Dan Fandrich via curl-library wrote:
> On Tue, Sep 06, 2022 at 11:57:24PM -0400, Dennis Clarke via curl-library
> wrote:
>> TESTFAIL: These test cases failed: 831 834 877 880 933 936 2023 2024 2026
>> 2027
>>
>> So not sure how to proceed. In the past I was generally able to get a
>> fantastic clean results from curl.
>>
>> So then ... how to proceed here ?
>
> If you run the tests using the -p and/or -v options, you'll get much
> more detailed information about why each test is failing.
This sort of thing is not very helpful at all :
.
.
.
test 0830...OK (663 out of 1512, remaining: 06:00, took 0.111s,
duration: 04:41)
test 0831...
831: protocol FAILED!
There was no content at all in the file log/server.input.
Server glitch? Total curl failure? Returned: 1
test 0833...OK (666 out of 1512, remaining: 05:58, took 0.119s,
duration: 04:42)
test 0834...
834: protocol FAILED!
There was no content at all in the file log/server.input.
Server glitch? Total curl failure? Returned: 1
test 0837...OK (669 out of 1512, remaining: 05:55, took 0.114s,
duration: 04:42)
.
.
.
So I am guessing that there is a way for me to re-run test 831 in
verbose detail.
-- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken GreyBeard and suspenders optional -- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2022-09-07