Re: [Bug-wget] Wget tests
wor...@alum.mit.edu (Dale R. Worley) writes: > Tim Rühsenwrites: >> Somethin went wrong... try again: > > I will investigate why this happened. Ugh. I had checked out a very old version of wget that didn't have Makefile.am, etc. After I fixed that, I discovered that older versions of Git do not handle submodules correctly if the path in $PWD uses symbolic links. So I've retrieved a newer version of Git to be able to work on wget. And there is at least one significant error in testenv/Test-Proto.py... Dale
Re: [Bug-wget] Wget tests
Tim Rühsenwrites: > Somethin went wrong... try again: Yes, you are correct. I repeated the "git clone", and the Makefile.am files are present in the new clone. E.g., the tests/Makefile.am clearly lists the Perl tests, and the Perl test files are present (e.g., tests/Test-auth-basic.px). Looking at my old working directory, tests/Makefile.am is missing but tests/Makefile is present. (It also contains the list of tests at "PX_TESTS =", but that is impossible to find unless you know the variable name to look for.) But the *.px files are missing. I will investigate why this happened. It appears that there is only one test for redirection behavior: testenv/Test-redirect-crash.py. Thanks for your assistance! Dale
Re: [Bug-wget] Wget tests
On Dienstag, 16. August 2016 11:23:04 CEST Dale R. Worley wrote: > Tim Rühsenwrites: > > We use standard automake tests (search the internet if you are interested > > in details). > > > > We have the 'legacy' tests/ directory with tests written in Perl. And the > > 'current' testenv/ directory with tests written in Python. > > > > See tests/Makefile.am resp. testenv/Makefile.am for the list of executed > > tests. > That points to part of the problem: I don't have those files in the Git > repository I downloaded from savannah.gnu.edu. ("git clone > git://git.savannah.gnu.org/wget.git") Somethin went wrong... try again: tim@debian:/tmp$ git clone git://git.savannah.gnu.org/wget.git Klone nach 'wget' ... remote: Counting objects: 29988, done. remote: Compressing objects: 100% (5909/5909), done. remote: Total 29988 (delta 23999), reused 29934 (delta 23968) Empfange Objekte: 100% (29988/29988), 12.20 MiB | 237.00 KiB/s, Fertig. Löse Unterschiede auf: 100% (23999/23999), Fertig. Prüfe Konnektivität ... Fertig. tim@debian:/tmp$ cd wget tim@debian:/tmp/wget$ ls -la insgesamt 852 drwxr-xr-x 15 tim tim 660 Aug 16 18:34 . drwxrwxrwt 27 root root580 Aug 16 18:33 .. -rw-r--r-- 1 tim tim2182 Aug 16 18:34 AUTHORS -rwxr-xr-x 1 tim tim 31606 Aug 16 18:34 bootstrap -rw-r--r-- 1 tim tim2040 Aug 16 18:34 bootstrap.conf drwxr-xr-x 2 tim tim 80 Aug 16 18:34 build-aux -rw-r--r-- 1 tim tim 814 Aug 16 18:34 cfg.mk -rw-r--r-- 1 tim tim 0 Aug 16 18:34 ChangeLog -rw-r--r-- 1 tim tim 682941 Aug 16 18:34 ChangeLog-2014-12-10 -rw-r--r-- 1 tim tim 24259 Aug 16 18:34 configure.ac drwxr-xr-x 2 tim tim 100 Aug 16 18:34 contrib -rw-r--r-- 1 tim tim 35147 Aug 16 18:34 COPYING drwxr-xr-x 2 tim tim 140 Aug 16 18:34 doc drwxr-xr-x 8 tim tim 260 Aug 16 18:34 .git -rw-r--r-- 1 tim tim1434 Aug 16 18:34 .gitignore -rw-r--r-- 1 tim tim 75 Aug 16 18:34 .gitmodules drwxr-xr-x 2 tim tim 40 Aug 16 18:34 gnulib drwxr-xr-x 2 tim tim 140 Aug 16 18:34 m4 -rw-r--r-- 1 tim tim1609 Aug 16 18:34 MAILING-LIST -rw-r--r-- 1 tim tim2909 Aug 16 18:34 Makefile.am drwxr-xr-x 2 tim tim 120 Aug 16 18:34 msdos -rw-r--r-- 1 tim tim 35669 Aug 16 18:34 NEWS drwxr-xr-x 2 tim tim 140 Aug 16 18:34 po -rw-r--r-- 1 tim tim4064 Aug 16 18:34 README -rw-r--r-- 1 tim tim 10220 Aug 16 18:34 README.checkout drwxr-xr-x 2 tim tim1640 Aug 16 18:34 src drwxr-xr-x 8 tim tim1000 Aug 16 18:34 testenv drwxr-xr-x 3 tim tim1940 Aug 16 18:34 tests -rw-r--r-- 1 tim tim 959 Aug 16 18:34 .travis.yml drwxr-xr-x 2 tim tim 160 Aug 16 18:34 util drwxr-xr-x 2 tim tim 380 Aug 16 18:34 vms -rw-r--r-- 1 tim tim 11 Aug 16 18:34 .x-sc_po_check -rw-r--r-- 1 tim tim 133 Aug 16 18:34 .x-sc_trailing_blank tim@debian:/tmp/wget$ ls -la */Makefile.am -rw-r--r-- 1 tim tim 3386 Aug 16 18:34 doc/Makefile.am -rw-r--r-- 1 tim tim 4076 Aug 16 18:34 src/Makefile.am -rw-r--r-- 1 tim tim 3749 Aug 16 18:34 testenv/Makefile.am -rw-r--r-- 1 tim tim 5671 Aug 16 18:34 tests/Makefile.am -rw-r--r-- 1 tim tim 1392 Aug 16 18:34 util/Makefile.am Regards, Tim signature.asc Description: This is a digitally signed message part.
Re: [Bug-wget] Wget tests
Tim Rühsenwrites: > We use standard automake tests (search the internet if you are interested in > details). > > We have the 'legacy' tests/ directory with tests written in Perl. And the > 'current' testenv/ directory with tests written in Python. > > See tests/Makefile.am resp. testenv/Makefile.am for the list of executed > tests. That points to part of the problem: I don't have those files in the Git repository I downloaded from savannah.gnu.edu. ("git clone git://git.savannah.gnu.org/wget.git") Dale
Re: [Bug-wget] Wget tests
On Montag, 15. August 2016 15:06:52 CEST Dale R. Worley wrote: > Can someone give me a hint how the wget tests work? The test > directories seem to contain no high-level documentation. As far as I > can tell, the pairs of files *.{trs,log} either are or correspond to the > various tests, but I can't find the file(s) that specify what the test > invocations of wget are, nor what files the test HTTP server sees. We use standard automake tests (search the internet if you are interested in details). We have the 'legacy' tests/ directory with tests written in Perl. And the 'current' testenv/ directory with tests written in Python. See tests/Makefile.am resp. testenv/Makefile.am for the list of executed tests. The output of each test executed by 'make check' is saved in a .log file. You can execute a single test with e.g. $ cd tests $ make check TESTS=Test--start-pos (creates a .log file) or with e.g. $ cd tests $ ./Test--start-pos.px (prints output on screen, creates no .log file) Regards, Tim signature.asc Description: This is a digitally signed message part.
Re: [Bug-wget] Wget tests
On Mon, 15 Aug 2016 15:06:52 -0400 wor...@alum.mit.edu (Dale R. Worley) wrote: > Can someone give me a hint how the wget tests work? The test > directories seem to contain no high-level documentation. As far as I > can tell, the pairs of files *.{trs,log} either are or correspond to the > various tests, but I can't find the file(s) that specify what the test > invocations of wget are, nor what files the test HTTP server sees. > > Thanks, > > Dale > I can tell you what worked for me to run the tests (take a look at the file INSTALL). $ wget -c http://ftp.gnu.org/gnu/wget/wget-1.18.tar.xz $ tar -xf wget-1.18.tar.xz $ cd wget-1.18 $ ./configure [your options here] $ make check to run some of the tests: $ cd tests $ make check - or - $ git clone git://git.savannah.gnu.org/wget.git $ cd wget $ ./bootstrap $ ./configure [your options here] $ make check Good luck, Matthew -- Matthew WhitepgpTxqF2Uyga3.pgp Description: PGP signature
[Bug-wget] Wget tests
Can someone give me a hint how the wget tests work? The test directories seem to contain no high-level documentation. As far as I can tell, the pairs of files *.{trs,log} either are or correspond to the various tests, but I can't find the file(s) that specify what the test invocations of wget are, nor what files the test HTTP server sees. Thanks, Dale