[Swan-dev] test run's log prints EXPECTATION FAILED lines from another run
D. Hugh Redelmeier
hugh at mimosa.com
Sat Jun 6 00:58:50 EEST 2015
Early this morning, I did a
make check UPDATE=1
and captured the log.
I found a bunch of mysterious EXPECTATION FAILED things in that log. They
pointed at lines that did not contain pexpect statements.
After thrashing about trying to explain the wrong line numbers, Paul
noticed that they came from greps of runs of a different date. So one
mystery was replaced by another.
My run started at Fri Jun 5 01:39:59 EDT 2015.
Why would this appear in my log?
grep 'EXPECTATION FAILED' /home/build/results/bluebird.mimosa.com/2015-06-03-bluebird.mimosa.com-v3.13aq6-365-g0ed8082-dirty-master/nat-pluto-10/OUTPUT/east.pluto.
log "northnet-eastnet-nat"[1] 192.1.2.254 #1: EXPECTATION FAILED at /source/programs/pluto/ikev1.c:2859: r != NULL
"northnet-eastnet-nat"[1] 192.1.2.254 #1: EXPECTATION FAILED at /source/programs/pluto/ikev1.c:2859: r != NULL
"northnet-eastnet-nat"[1] 192.1.2.254 #1: EXPECTATION FAILED at /source/programs/pluto/ikev1.c:2859: r != NULL
"northnet-eastnet-nat"[1] 192.1.2.254 #1: EXPECTATION FAILED at /source/programs/pluto/ikev1.c:2859: r != NULL
"northnet-eastnet-nat"[1] 192.1.2.254 #1: EXPECTATION FAILED at /source/programs/pluto/ikev1.c:2859: r != NULL
"northnet-eastnet-nat"[1] 192.1.2.254 #1: EXPECTATION FAILED at /source/programs/pluto/ikev1.c:2859: r != NULL
"northnet-eastnet-nat"[1] 192.1.2.254 #2: EXPECTATION FAILED at /source/programs/pluto/ikev1.c:2859: r != NULL
"northnet-eastnet-nat"[1] 192.1.2.254 #2: EXPECTATION FAILED at /source/programs/pluto/ikev1.c:2859: r != NULL
"northnet-eastnet-nat"[1] 192.1.2.254 #2: EXPECTATION FAILED at /source/programs/pluto/ikev1.c:2859: r != NULL
"northnet-eastnet-nat"[1] 192.1.2.254 #2: EXPECTATION FAILED at /source/programs/pluto/ikev1.c:2859: r != NULL
Why does it look through this other run???? I'm not sure what "it"
is.
This violates the Principle of Least Astonishment.
More information about the Swan-dev
mailing list