Re: [Swan-dev] status of failing tests

2018-03-06 Thread Paul Wouters
On Tue, 6 Mar 2018, Andrew Cagney wrote: testing/pluto/ikev2-ppk-static-05-insist-nokey-insist-fail failed There's something special about that test preventing "addconn" from exiting (infinite loop)? It's nothing related to the specific test... I just ran it against git master on my

Re: [Swan-dev] status of failing tests

2018-03-06 Thread Andrew Cagney
>> testing/pluto/ikev2-ppk-static-05-insist-nokey-insist-fail failed >> west:output-different >> -003 "westnet-eastnet-ipv4-psk-ppk" #1: connection requires PPK, >> but PPK_ID did not match any loaded PPK >> +003 "westnet-eastnet-ipv4-psk-ppk" #1: connection requires PPK, >> but

Re: [Swan-dev] status of failing tests

2018-02-13 Thread Paul Wouters
On Tue, 13 Feb 2018, Andrew Cagney wrote: I'm left wondering if it would be easier to have a separate script (kvmrun.py?) that always stops at final.sh and requires/allows only one test. That would work for me. Paul ___ Swan-dev mailing list

Re: [Swan-dev] status of failing tests

2018-02-13 Thread Andrew Cagney
On 4 February 2018 at 16:19, Paul Wouters wrote: > On Fri, 2 Feb 2018, Andrew Cagney wrote: > - early stop? testing/pluto/klips-netkey-pluto-06 failed east:output-different west:output-different >>> >>> >>> >>> if final.sh runs a status or trafficstatus and also

Re: [Swan-dev] status of failing tests

2018-02-04 Thread Paul Wouters
On Fri, 2 Feb 2018, Andrew Cagney wrote: - early stop? testing/pluto/klips-netkey-pluto-06 failed east:output-different west:output-different if final.sh runs a status or trafficstatus and also shuts down pluto for a leak report, there is a race between nodes. If one shuts down fast, the

Re: [Swan-dev] status of failing tests

2018-02-02 Thread Andrew Cagney
>> - early stop? >> testing/pluto/klips-netkey-pluto-06 failed east:output-different >> west:output-different > > > if final.sh runs a status or trafficstatus and also shuts down pluto for > a leak report, there is a race between nodes. If one shuts down fast, > the other won't see the proper

Re: [Swan-dev] status of failing tests

2018-02-02 Thread Andrew Cagney
FYI ... On 1 February 2018 at 11:37, Paul Wouters wrote: > On Thu, 1 Feb 2018, D. Hugh Redelmeier wrote: > >> - several failures that were only IKE retransmissions. Just ignore them. >> But a bit weird when IMPAIR_RETRANSMITS is set. > > > can happen in IKEv1 were both ends

Re: [Swan-dev] status of failing tests

2018-02-01 Thread Paul Wouters
On Thu, 1 Feb 2018, D. Hugh Redelmeier wrote: - several failures that were only IKE retransmissions. Just ignore them. But a bit weird when IMPAIR_RETRANSMITS is set. can happen in IKEv1 were both ends retransmit? - not sure: maybe retransmission needed but suppressed?

Re: [Swan-dev] status of failing tests

2018-01-31 Thread D. Hugh Redelmeier
| From: Paul Wouters | The tests seem to have gotten fairly consistent. There is a still a | group of problems: Thanks for a summary. I've got some fairly safe changes that I wanted to test. I ran these tests on the weekend. I started with master, as of

Re: [Swan-dev] status of failing tests

2018-01-26 Thread Paul Wouters
On Fri, 26 Jan 2018, Antony Antony wrote: There is an odd thing in master, I suspect latest tag commit is not yet merged to master. make showversion 3.22-773-gaafe4eba2-master Ahh. we tried to leave the tag on the release-3.23 branch so we did not have to commit, tag, uncommit the version