On Wednesday, March 22, 2017 11:39:59 AM CET Avinash Sonawane wrote: > Hello! > > As I have mentioned earlier I have built and installed wget2 on my > system. But I hadn't performed `male check` since I wasn't about to > write unit tests. > > But now as I am extending tests/test-parse-html.c to include new unit > tests I did `make check`. > > Now there are two problems: > 1) make check is utterly slow. I can see my CPU usage going up to > 1-2%. That's it! It's almost an hour or and it's still running with > this output: > FAIL: test > FAIL: test-wget-1 > FAIL: test-restrict-ascii > FAIL: test-i-http > FAIL: test-i-https > FAIL: test-np > FAIL: test--spider-r > FAIL: test-meta-robots > FAIL: test-idn-robots > FAIL: test-idn-meta > FAIL: test-idn-cmd > FAIL: test-iri > FAIL: test-iri-percent > FAIL: test-iri-list > FAIL: test-iri-forced-remote > FAIL: test-auth-basic > PASS: test-parse-html > ... > > How much time does it take usually? I haven't configured to use Valgrind > yet. > > 2) All the tests before test-parse-html have failed and it's still > running so have no idea how many more will fail. Let me remind you I'm > performing `make check` on fresh clone and haven't modified it in any > manner. Is this an expected behavior? What does FAIL tests mean? Can > we do something about them?
That's interesting, never saw that. No CPU and still long waiting times means either networking or pthreads is broken. 'make check' normally should just take a few seconds. Valgrind tests a bit more, but less than or around 1 minute. Did you install all prerequisites ?(see output from ./configure) Send us your config.log and tests/test.log. Regards, Tim
signature.asc
Description: This is a digitally signed message part.
