[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-wget] [Bug-Wget] Issues with Perl-based test suite
From: |
Darshit Shah |
Subject: |
Re: [Bug-wget] [Bug-Wget] Issues with Perl-based test suite |
Date: |
Tue, 30 Sep 2014 21:42:34 +0530 |
User-agent: |
Mutt/1.5.23 (2014-03-12) |
On 09/30, Tim Rühsen wrote:
On Sunday 28 September 2014 01:23:08 Darshit Shah wrote:
2. Race Conditions: The tets suite seems to have some races somewhere in it.
Over the last year or so, I've often seen Test-proxied-https.px fail and
then pass in the second invokation. This seemed like some race, but
occurred infrequently enopugh to be a pain point. However, Tim's recent
patch for using the parallel tets harness seems to be causing more tests to
fail for me. Now I have all the Test-iri* tests also failing very randomly
and erratically. A second/third/nth invokation of make check will generally
see them pass successfully. Without Tim's patch, these tests always passed
without issues. I'm loath to believe that the patch itself is the cause of
failure. My understanding is that, it is only triggering the issue more
often leading to a very high rate of false positives.
Well Darshit, I just saw it happen here :-)
FAIL: Test-N-no-info.px
But the content of the .log file looks good:
#############
Running test Test-N-current
Calling ../src/wget -N http://localhost:47392/somefile.txt
--2014-09-30 09:42:01-- http://localhost:47392/somefile.txt
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:47392... connected.
HTTP request sent, awaiting response... 200 Dontcare
Length: unspecified [text/plain]
Last-modified header missing -- time-stamps turned off.
--2014-09-30 09:42:01-- http://localhost:47392/somefile.txt
Connecting to localhost (localhost)|127.0.0.1|:47392... connected.
HTTP request sent, awaiting response... 200 Dontcare
Length: 112 [text/plain]
Saving to: 'somefile.txt'
0K 100% 11.7M=0s
2014-09-30 09:42:01 (11.7 MB/s) - 'somefile.txt' saved [112/112]
Test successful.
#############
I just want to confirm that there is a race condition. I'll look at that
later. It has nothing to do with my ongoing patch.
Tim
--- end quoted text ---
So I'm not the only one experiencing them. :)
I just came across another issue, not sure if it is indeed caused by a race
condition. Test-proxied-https.px failed with the following output:
--2014-09-30 21:37:25-- https://no.such.domain/needs-auth.txt
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:37161... failed: Connection refused.
Connecting to localhost (localhost)|127.0.0.1|:37161... connected.
WARNING: cannot verify no.such.domain's certificate, issued by
'/C=US/ST=California/L=Santa Claa/O=Internet Widgits Pty Ltd/CN=Micah
Cowan/address@hidden':
Self-signed certificate encountered.
WARNING: certificate common name 'Micah Cowan' doesn't match requested host
name 'no.such.domain'.
Proxy request sent, awaiting response... 401 Unauthorized
Reusing existing connection to no.such.domain:443.
Proxy request sent, awaiting response... No data received.
Retrying.
--2014-09-30 21:37:26-- (try: 2) https://no.such.domain/needs-auth.txt
Got code: 256
That's a very random failure I'd say. And running the test again promptly fixed
it.
--
Thanking You,
Darshit Shah
pgp4IPC_BsfXS.pgp
Description: PGP signature