Project

General

Profile

[Solved] Lighty 1.4.60 make check failure

Added by maxentry about 2 months ago

I compiled lighttpd 1.4.60 successfully but when I run the make check command, I get fails (message says I should report this here). here's what I ran:
1. rm -f config.cache #I had an issue earlier, so I first clear the configuration cache
2. ./autogen.sh
3. ./configure -C --enable-mmap --with-brotli --with-bzip2 --with-lua --with-maxminddb --with-memcached --with-openssl --with-pcre --prefix=/usr/local/bin/1.4.60/
4. make -j 4
5. make check

Here's the console output:

Making check in src
make  check-am
make  check-TESTS
PASS: t/test_array
PASS: t/test_buffer
PASS: t/test_burl
PASS: t/test_base64
PASS: t/test_configfile
PASS: t/test_keyvalue
PASS: t/test_mod_access
PASS: t/test_mod_evhost
PASS: t/test_mod_indexfile
PASS: t/test_mod_simple_vhost
PASS: t/test_mod_staticfile
PASS: t/test_mod_userdir
PASS: t/test_request
===================
All 13 tests passed
===================
Making check in doc
Making check in config
Making check in conf.d
Making check in vhosts.d
Making check in scripts
Making check in systemd
Making check in outdated
Making check in tests
Making check in docroot
make  fcgi-responder scgi-responder
depbase=`echo fcgi-responder.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
gcc -DHAVE_CONFIG_H -I. -I..   -D_REENTRANT  -D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGE_FILES  -g -O2 -pipe -Wall -W -Wshadow -pedantic -MT fcgi-responder.o -MD -MP -MF $depbase.Tpo -c -o fcgi-responder.o fcgi-responder.c &&\
mv -f $depbase.Tpo $depbase.Po
/bin/bash ../libtool  --tag=CC   --mode=link gcc  -g -O2 -pipe -Wall -W -Wshadow -pedantic   -o fcgi-responder fcgi-responder.o
libtool: link: gcc -g -O2 -pipe -Wall -W -Wshadow -pedantic -o fcgi-responder fcgi-responder.o
depbase=`echo scgi-responder.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
gcc -DHAVE_CONFIG_H -I. -I..   -D_REENTRANT  -D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGE_FILES  -g -O2 -pipe -Wall -W -Wshadow -pedantic -MT scgi-responder.o -MD -MP -MF $depbase.Tpo -c -o scgi-responder.o scgi-responder.c &&\
mv -f $depbase.Tpo $depbase.Po
/bin/bash ../libtool  --tag=CC   --mode=link gcc  -g -O2 -pipe -Wall -W -Wshadow -pedantic   -o scgi-responder scgi-responder.o
libtool: link: gcc -g -O2 -pipe -Wall -W -Wshadow -pedantic -o scgi-responder scgi-responder.o
make  check-TESTS
Testing in build directory: '..' and cwd: '/root/lighttpd-1.4.60/tests'
preparing infrastructure                PASS: prepare.sh
./core-condition.t .. Bareword "POSIX::WNOHANG" not allowed while "strict subs" in use at LightyTest.pm line 140.
Compilation failed in require at ./core-condition.t line 12.
BEGIN failed--compilation aborted at ./core-condition.t line 12.
# Looks like your test exited with 255 before it could output anything.
./core-condition.t .. Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 25/25 subtests
./mod-fastcgi.t ..... Bareword "POSIX::WNOHANG" not allowed while "strict subs" in use at LightyTest.pm line 140.
Compilation failed in require at ./mod-fastcgi.t line 11.
BEGIN failed--compilation aborted at ./mod-fastcgi.t line 11.
# Looks like your test exited with 255 before it could output anything.
./mod-fastcgi.t ..... Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 24/24 subtests
./mod-scgi.t ........ Bareword "POSIX::WNOHANG" not allowed while "strict subs" in use at LightyTest.pm line 140.
Compilation failed in require at ./mod-scgi.t line 11.
BEGIN failed--compilation aborted at ./mod-scgi.t line 11.
# Looks like your test exited with 255 before it could output anything.
./mod-scgi.t ........ Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 10/10 subtests
./request.t ......... Bareword "POSIX::WNOHANG" not allowed while "strict subs" in use at LightyTest.pm line 140.
Compilation failed in require at ./request.t line 12.
BEGIN failed--compilation aborted at ./request.t line 12.
# Looks like your test exited with 255 before it could output anything.
./request.t ......... Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 179/179 subtests

Test Summary Report
-------------------
./core-condition.t (Wstat: 65280 Tests: 0 Failed: 0)
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 25 tests but ran 0.
./mod-fastcgi.t   (Wstat: 65280 Tests: 0 Failed: 0)
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 24 tests but ran 0.
./mod-scgi.t      (Wstat: 65280 Tests: 0 Failed: 0)
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 10 tests but ran 0.
./request.t       (Wstat: 65280 Tests: 0 Failed: 0)
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 179 tests but ran 0.
Files=4, Tests=0,  1 wallclock secs ( 0.04 usr  0.01 sys +  0.22 cusr  0.05 csys =  0.32 CPU)
Result: FAIL
Failed 4/4 test programs. 0/0 subtests failed.
FAIL: run-tests.pl
cleaning up                             PASS: cleanup.sh
========================================================================
1 of 3 tests failed
Please report to https://redmine.lighttpd.net/projects/lighttpd/boards/2
========================================================================
Makefile:650: recipe for target 'check-TESTS' failed
make[3]: *** [check-TESTS] Error 1
Makefile:798: recipe for target 'check-am' failed
make[2]: *** [check-am] Error 2
Makefile:557: recipe for target 'check-recursive' failed
make[1]: *** [check-recursive] Error 1
Makefile:470: recipe for target 'check-recursive' failed
make: *** [check-recursive] Error 1

Replies (5)

RE: [Solved] Lighty 1.4.60 make check failure - Added by gstrauss about 2 months ago

Thanks. This was recently fixed in #3110

RE: [Solved] Lighty 1.4.60 make check failure - Added by maxentry about 2 months ago

Thanks for the response.
I just applied the fix mentioned in that issues to tests/lightyTest.pm by replacing line 140 with

 if (0 != waitpid($child, POSIX::WNOHANG())) {

but I still get same the error. Thoughts?

RE: [Solved] Lighty 1.4.60 make check failure - Added by maxentry about 2 months ago

Apologies, scrap the last reply.
I actually get different errors. Here's the relevant snippet

make  check-TESTS
Testing in build directory: '..' and cwd: '/root/lighttpd-1.4.60/tests'
preparing infrastructure                PASS: prepare.sh
./core-condition.t .. Bareword "Fcntl::F_SETFD" not allowed while "strict subs" in use at LightyTest.pm line 217.
Compilation failed in require at ./core-condition.t line 12.
BEGIN failed--compilation aborted at ./core-condition.t line 12.
# Looks like your test exited with 255 before it could output anything.
./core-condition.t .. Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 25/25 subtests
./mod-fastcgi.t ..... Bareword "Fcntl::F_SETFD" not allowed while "strict subs" in use at LightyTest.pm line 217.
Compilation failed in require at ./mod-fastcgi.t line 11.
BEGIN failed--compilation aborted at ./mod-fastcgi.t line 11.
# Looks like your test exited with 255 before it could output anything.
./mod-fastcgi.t ..... Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 24/24 subtests
./mod-scgi.t ........ Bareword "Fcntl::F_SETFD" not allowed while "strict subs" in use at LightyTest.pm line 217.
Compilation failed in require at ./mod-scgi.t line 11.
BEGIN failed--compilation aborted at ./mod-scgi.t line 11.
# Looks like your test exited with 255 before it could output anything.
./mod-scgi.t ........ Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 10/10 subtests
./request.t ......... Bareword "Fcntl::F_SETFD" not allowed while "strict subs" in use at LightyTest.pm line 217.
Compilation failed in require at ./request.t line 12.
BEGIN failed--compilation aborted at ./request.t line 12.
# Looks like your test exited with 255 before it could output anything.
./request.t ......... Dubious, test returned 255 (wstat 65280, 0xff00)

RE: [Solved] Lighty 1.4.60 make check failure - Added by maxentry about 2 months ago

Apologies for spamming the tread. Fixed the error by changing line 216 from:

fcntl($SOCK, Fcntl::F_SETFD(), 0); # clr FD_CLOEXEC

to

fcntl($SOCK, Fcntl::F_SETFD(), 0); # clr FD_CLOEXEC

PS: My error above shows as 217 because I inserted extra line when applying the fix for the first error on line 117

    (1-5/5)