Build failures on master?!

Matt Caswell matt at openssl.org
Mon Dec 23 12:48:13 UTC 2019 


On 22/12/2019 22:26, Dr. Matthias St. Pierre wrote:
>> With apologies for being a week behind on mail, but I didn't see any
>> commits in the past week that look like they were targetted to fix external
>> tests, and I see (E.g.)
>> https://travis-ci.org/openssl/openssl/jobs/628003784?utm_medium=notification&utm_source=github_status
>> succeeding (as well as my local build with the krb5 tests).  Are the
>> external tests still failing?
> 
> I don't really understand what's going on, but it looks like job 19 fails intermittently: Job #30814.19 (the one you 
> pointet out) succeeded, but #30827.19 failed. And afterwards #30846.19 succeeded again.
> 
> - #30814.19 (two days ago): SUCCEEDED
>   https://travis-ci.org/openssl/openssl/jobs/628003784?utm_medium=notification&utm_source=github_status
> 
> 
> - #30827.19 (23 hours ago): FAILED
>   https://travis-ci.org/openssl/openssl/jobs/628205488?utm_medium=notification&utm_source=github_status
> 
>     Test Summary Report
>     -------------------
>     95-test_external_krb5.t     (Wstat: 256 Tests: 1 Failed: 1)
>       Failed test:  1

AFAICT the krb5 test failure on master seems to be environmental. We get
this failure:

make[5]: Entering directory
'/home/travis/build/openssl/openssl/krb5/src/lib/rpc/unit-test'
rm -f krb5cc_rpc_test_*
../../../kadmin/testing/scripts/env-setup.sh
../../../kadmin/testing/scripts/start_servers
RPC_TEST_SRVTAB=/tmp/rpc_test_v5srvtab.$$ ; export RPC_TEST_SRVTAB ; \
trap "echo Failed, cleaning up... ; rm -f $RPC_TEST_SRVTAB ;
../../../kadmin/testing/scripts/env-setup.sh
../../../kadmin/testing/scripts/stop_servers   ; trap '' 0 ; exit 1" 0 1
2 3 14 15 ; \
if ../../../kadmin/testing/scripts/env-setup.sh \
	runtest --debug --srcdir . --host x86_64-pc-linux-gnu SERVER=./server
CLIENT=./client \
	KINIT=../../../clients/kinit/kinit \
	KDESTROY=../../../clients/kdestroy/kdestroy \
	PRIOCNTL_HACK=0 VALGRIND="" \
	PASS="tcp" --tool rpc_test  ; \
then \
	echo Cleaning up... ; \
	rm -f $RPC_TEST_SRVTAB krb5cc_rpc_test_* ; \
	../../../kadmin/testing/scripts/env-setup.sh
../../../kadmin/testing/scripts/stop_servers   ; \
	trap 0 ; exit 0 ; \
else exit 1 ; fi
WARNING: Couldn't find tool init file
Test Run By travis on Thu Dec 19 08:07:45 2019
Native configuration is x86_64-pc-linux-gnu

		=== rpc_test tests ===

Schedule of variations:
    unix

Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file
for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for
target.
Using ./config/unix.exp as tool-and-target-specific interface file.
TOP=/home/travis/build/openssl/openssl/krb5/src/kadmin
Running pass `tcp' ...
Running ./rpc_test.0/expire.exp ...
FAIL: tcp: expire: client 1: unexpected return status 2, should be 0.
FAIL: tcp: expire: client 2: unexpected return status 2, should be 0.
FAIL: tcp: expire: client 3: unexpected return status 2, should be 0.
Running ./rpc_test.0/fullrun.exp ...
FAIL: tcp: full run: client fullrun: unexpected return status 2, should
be 0.
FAIL: tcp: fullrun: echo test: expected 11 dots, got 1
FAIL: tcp: fullrun: expected four bad verifiers, got 0
Running ./rpc_test.0/gsserr.exp ...
FAIL: tcp: gss err: timeout waiting for server output

		=== rpc_test Summary ===

# of expected passes		2
# of unexpected failures	7
./client version <unknown>
./server version <unknown>
Failed, cleaning up...
Makefile:678: recipe for target 'unit-test-body' failed



However, if I run the same test locally with the same config options the
krb5 tests pass. This is the equivalent section of the log:


make[5]: Entering directory
'/home/matt/dev/openssl-write/krb5/src/lib/rpc/unit-test'
rm -f krb5cc_rpc_test_*
../../../kadmin/testing/scripts/env-setup.sh
../../../kadmin/testing/scripts/start_servers
RPC_TEST_SRVTAB=/tmp/rpc_test_v5srvtab.$$ ; export RPC_TEST_SRVTAB ; \
trap "echo Failed, cleaning up... ; rm -f $RPC_TEST_SRVTAB ;
../../../kadmin/testing/scripts/env-setup.sh
../../../kadmin/testing/scripts/stop_servers   ; trap '' 0 ; exit 1" 0 1
2 3 14 15 ; \
if ../../../kadmin/testing/scripts/env-setup.sh \
	runtest --debug --srcdir . --host x86_64-pc-linux-gnu SERVER=./server
CLIENT=./client \
	KINIT=../../../clients/kinit/kinit \
	KDESTROY=../../../clients/kdestroy/kdestroy \
	PRIOCNTL_HACK=0 VALGRIND="" \
	PASS="tcp" --tool rpc_test  ; \
then \
	echo Cleaning up... ; \
	rm -f $RPC_TEST_SRVTAB krb5cc_rpc_test_* ; \
	../../../kadmin/testing/scripts/env-setup.sh
../../../kadmin/testing/scripts/stop_servers   ; \
	trap 0 ; exit 0 ; \
else exit 1 ; fi
WARNING: Couldn't find tool init file
Test run by matt on Mon Dec 23 12:26:44 2019
Native configuration is x86_64-pc-linux-gnu

		=== rpc_test tests ===

Schedule of variations:
    unix

Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file
for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for
target.
Using ./config/unix.exp as tool-and-target-specific interface file.
TOP=/home/matt/dev/openssl-write/krb5/src/kadmin
Running pass `tcp' ...
Running ./rpc_test.0/expire.exp ...
Running ./rpc_test.0/fullrun.exp ...
Running ./rpc_test.0/gsserr.exp ...

		=== rpc_test Summary ===

# of expected passes		8
./client version <unknown>
./server version <unknown>
Cleaning up...
make[5]: Leaving directory
'/home/matt/dev/openssl-write/krb5/src/lib/rpc/unit-test'




>       Non-zero exit status: 1
>     95-test_external_pyca.t     (Wstat: 256 Tests: 1 Failed: 1)
>       Failed test:  1
>       Non-zero exit status: 1
>     Files=3, Tests=3, 225 wallclock secs ( 0.67 usr  0.05 sys + 112.06 cusr 29.38 csys = 142.16 CPU)
>     Result: FAIL
>     Makefile:2893: recipe for target '_tests' failed
>     make[1]: *** [_tests] Error 1
>     make[1]: Leaving directory '/home/travis/build/openssl/openssl'
>     Makefile:2891: recipe for target 'tests' failed
>     make: *** [tests] Error 2
>     ** FAILED -- MAKE TEST
> 
> - #30846.19 (2 hours ago) SUCCEEDED
>   https://travis-ci.org/openssl/openssl/jobs/628466771?utm_medium=notification&utm_source=github_status
> 
> There are other tests failing, too. If you look at the build history, you will hardly see any successful builds on
> master and 1.1.1.
> 
> https://travis-ci.org/openssl/openssl/builds?utm_medium=notification&utm_source=github_status
> 
> 
> Matthias
> 
> 
>

More information about the openssl-project mailing list