[Swan-dev] some test failures

D. Hugh Redelmeier hugh at mimosa.com
Tue Oct 3 14:23:11 UTC 2017


I ran the tests with the source as of about 2:00 AM Sunday morning +
my pending changes.
The results from testing are still a mess.
I cannot make progress on testing my stuff with so much noise.
I'm giving up on this run.
Here is an analysis of a few of the failures.

If you are responsible for a test failure, or know what is going on PLEASE FIX IT.


testing/pluto/ikev1-algo-05-3des-sha2/OUTPUT/west.console.diff just RETRANSMISSION
testing/pluto/ikev2-11-simple-psk/OUTPUT/west.console.diff just RETRANSMISSION
testing/pluto/ikev2-27-uniqueid/OUTPUT/north.console.diff just RETRANSMISSION
testing/pluto/ikev2-algo-sha2-06/OUTPUT/west.console.diff just RETRANSMISSION
testing/pluto/interop-ikev2-strongswan-04-x509-responder/OUTPUT/west.console.diff just RETRANSMISSION
testing/pluto/interop-ikev2-strongswan-19-x509-res-certreq/OUTPUT/west.console.diff just RETRANSMISSION
testing/pluto/interop-ikev2-strongswan-27-fragmentation/OUTPUT/west.console.diff just RETRANSMISSION
testing/pluto/netkey-tfc-01/OUTPUT/west.console.diff just RETRANSMISSION

testing/pluto/ah-pluto-07-klips-netkey/OUTPUT/.console.diff failed west:output-different
Kind of interesting.
	switched from "westnet-eastnet-ah-md5" to "westnet-eastnet-ah-sha1"
and many othr differences

testing/pluto/algo-pluto-10/OUTPUT/.console.diff failed west:output-different
retransmission + discarding packet received during asynchronous work (DNS or crypto) in STATE_QUICK_I1

testing/pluto/basic-pluto-02/OUTPUT/.console.diff failed east:output-different west:output-different
testing/pluto/compress-pluto-01/OUTPUT/.console.diff failed east:output-different west:output-different
east: a lot of changed XFRM state info.  Why?
west: retransmission + discarding packet received during asynchronous work (DNS or crypto) in STATE_QUICK_I1

testing/pluto/certoe-07-nat-2-clients/OUTPUT/.console.diff failed east:output-different road:output-different
east: different amount of traffic
road: another XFRM SA?

testing/pluto/certoe-08-nat-packet-cop-restart/OUTPUT/.console.diff failed road:output-different
different ammount of traffic?  Amount not scrubbed, nor id scrubbed?
-icmp     1 27 src=192.1.3.209 dst=192.1.2.23 type=8 code=0 id=XXXX src=192.1.2.23 dst=10.0.10.1 type=0 code=0 id=XXXX mark=0 secctx=system_u:object_r:unlabeled_t:s0 use=1
+icmp     1 29 src=192.1.3.209 dst=192.1.2.23 type=8 code=0 id=1881 src=192.1.2.23 dst=10.0.10.1 type=0 code=0 id=1881 mark=0 secctx=system_u:object_r:unlabeled_t:s0 use=1
script changed:
- conntrack -L -n
+ conntrack -L -n | sed "s/id=[0-9]*/id=XXXX/g"
IP addresses changed:
packet cont changed:
-icmp     1 16 src=192.1.3.209 dst=192.1.2.23 type=8 code=0 id=XXXX src=192.1.2.23 dst=192.1.3.209 type=0 code=0 id=XXXX mark=0 secctx=system_u:object_r:unlabeled_t:s0 use=1
+icmp     1 17 src=192.1.3.209 dst=192.1.2.23 type=8 code=0 id=XXXX src=192.1.2.23 dst=192.1.3.209 type=0 code=0 id=XXXX mark=0 secctx=system_u:object_r:unlabeled_t:s0 use=1

testing/pluto/delete-sa-01/OUTPUT/.console.diff failed east:output-different west:output-different
+whack error: "SAwest-east" unexpected argument "leftrsasigkey"

testing/pluto/delete-sa-03/OUTPUT/.console.diff failed east:output-different west:output-different
west: divergence starts +002 "west-east" #1: switched from "west-east" to "west-east-c"

east: divergence starts:
-000 "west-east": 192.1.2.23<192.1.2.23>[@east]...192.1.2.45<192.1.2.45>[@west]; prospective erouted; eroute owner: #0
+000 "west-east": 192.1.2.23<192.1.2.23>[@east]...192.1.2.45<192.1.2.45>[@west]; erouted; eroute owner: #2


testing/pluto/delete-sa-04/OUTPUT/.console.diff failed east:output-different west:output-different
These differences might be due to some sanitizer problem or script change.  But more is going on.
- ipsec status |grep EVENT_v1_RETRANSMIT | sed "s/EVENT_v1_RETRANSMIT in /EVENT_v1_RETRANSMIT in .../"
+ ipsec status |grep EVENT_v1_RETRANSMIT | sed "s/EVENT_v1_RETRANSMIT in .*$/EVENT_v1_RETRANSMIT in .../"
A delete does not happen on west.



More information about the Swan-dev mailing list