[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-wget] 'Test--https.py' and 'Test--https-crl.py' failing when no

From: Tim Ruehsen
Subject: Re: [Bug-wget] 'Test--https.py' and 'Test--https-crl.py' failing when no SSL support
Date: Mon, 22 Jun 2015 11:22:19 +0200
User-agent: KMail/4.14.2 (Linux/4.0.0-1-amd64; KDE/4.14.2; x86_64; ; )

On Sunday 21 June 2015 12:08:39 Ander Juaristi wrote:
> Hi all,
> I noticed that when Wget is compiled with no SSL support, two tests from the
> Python test suite fail. For me it's always reproducible:
>    $ ./configure --without-ssl
>    $ make check
>    <output trimmed>
>    FAIL: Test--https.py
>    FAIL: Test--https-crl.py
> This doesn't look like desired behaviour, does it? Ideally, those tests
> should be skipped when Wget does not support SSL.

> Isn't there anything like WgetFeature.pm in the Python tests?

Today we have the possibility to work with XFAIL_TESTS in Makefile.am.

How it should work (IMO):
When we './configure --without-ssl' we expect the https tests to FAIL (not 
just SKIPPED). What we simply need is a SUBST variable that we check in 
testenv/Makefile.am. Depending on the check the https tests are either added 
to TESTS or to XFAIL_TESTS. Same with other switchable features.

What do you think ?


Attachment: signature.asc
Description: This is a digitally signed message part.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]