[Top][All Lists]

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

Re: wget 1.21.2 checks failing with unexpected extra downloaded files

From: Darshit Shah
Subject: Re: wget 1.21.2 checks failing with unexpected extra downloaded files
Date: Wed, 01 Dec 2021 23:15:17 +0100
User-agent: Cyrus-JMAP/3.5.0-alpha0-4458-g51a91c06b2-fm-20211130.004-g51a91c06

Hi Brian,

Thanks for the report and sorry for the delay it has taken me to respond to 
your email.

This is indeed something weird. You are right in your guess that it happens 
because of the wget-log file being created. 
I will have to try and reproduce this issue in a Cygwin environment at some 
point, since I don't have a Windows machine on hand.

However, I can't recollect any change in the 1.21.2 release that would cause 
Wget to redirect to the log file in a new scenario. So, I have to ask, has 
something changed in your environment?
Wget will automatically redirect to wget-log if it identifies that stdout 
/stderr are not connected to a terminal.

In either case, I'd love to fix this in a way that works in your environment 
because the tests should always run. 

On Sun, Sep 26, 2021, at 23:45, Brian Inglis wrote:
> Latest wget 1.21.2 checks are all failing with unexpected extra files 
> being downloaded under latest Cygwin 3.0.2 (under Windows 2020H2 with 
> updates to 2021-August).
> I have also tried building with and without autoreconf without change.
> The issue appears under both 64 and 32 bit environments and under our 
> Github Actions scallywag CI servers with minimal installs of only the 
> required (Cygwin) lib...-devel etc. packages for building and testing.
> The relevant test-suite.log files have been attached, lightly "sanitized 
> for my protection".
> Never had any problems with test failures (except unsupported IRI) 
> building any previous releases under either Cygwin arch.
> Is there any chance that files e.g. wget-log are being created or saved 
> in directories differing *only* from the download directories by *case*, 
> or by some unexpected *encoding* difference, due to file name characters 
> prohibited by the underlying Windows filesystem, somewhere in the path, 
> or an unexpected location?
> Have there been any significant changes in testing requirements or 
> utilities?
> Could there be any issues from including updated gnulib m4 macros?
> I have had a couple of recent issues with other packages requiring 
> tweaks to gnulib m4 macros.
> Please let me know if there is any further diagnosis I can do or 
> information I can provide to assist with resolving this issue.
> -- 
> Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
> This email may be disturbing to some readers as it contains
> too much technical detail. Reader discretion is advised.
> [Data in binary units and prefixes, physical quantities in SI.]
> Attachments:
> * testenv-test-suite.log
> * tests-test-suite.log

reply via email to

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