[Swan-dev] testing hangs for me
Andrew Cagney
andrew.cagney at gmail.com
Thu Mar 7 15:00:36 UTC 2019
Hugh,
The testing machine might be hitting this problem (yesterday it hung
twice) so I crippled it.
On the machine that hangs, have you tried a run with KVM_WORKERS unset
and/or KVM_PREFIXES with only one entry?
Just note that, before changing KVM_PREFIXES, a kvm-purge is strongly
recommended vis
- make kvm-purge
- modify KVM_PREFIXES
- make kvm-install
else, the domains for the removed prefixes loiter making for very
confusing KVM errors.
On Mon, 28 Jan 2019 at 01:47, D. Hugh Redelmeier <hugh at mimosa.com> wrote:
>
> Twice today I've tried to run the test suite. Twice it has hung after
> less than half an hour.
>
> The first time I started with "make kvm-clean".
> The second time I started with "make kvm-purge".
>
> I gave up and commited my changes without testing. I hope that they work.
>
> Host system: Fedora 29 with all updates as of yesterday.
>
> here's the current relevant process tree for the second hang:
>
> 0 1105 15846 3207 20 0 215328 2492 x64_sy S+ pts/1 0:00 | | \_ script -a tests.LOG032.much
> 0 1105 15848 15846 20 0 218080 5448 - Ss pts/2 0:00 | | \_ bash -i
> 0 1105 20132 15848 20 0 224460 5836 - S+ pts/2 0:00 | | \_ make kvm-check
> 0 1105 21405 20132 20 0 529184 44920 - Sl+ pts/2 0:47 | | \_ python3 /home/build/libreswan/testing/utils/kvmrunner.py --prefix a. --prefix b. --workers 2 --publish-hash 73c4e70fe1c0988fb1e12596ac718dcadbf2abca --publish-results ./RESULTS/v3.27-707-g73c4e70fe-master --publish-status ./RESULTS/status.json --test-status good testing/pluto
> 4 0 27797 21405 20 0 232176 10144 - Ss+ pts/5 0:00 | | \_ /usr/bin/sudo virsh --connect qemu:///system console --force b.west
> 4 0 27799 27797 20 0 318584 13948 - Sl+ pts/5 0:01 | | | \_ virsh --connect qemu:///system console --force b.west
> 4 0 27801 21405 20 0 232176 10152 - Ss+ pts/11 0:00 | | \_ /usr/bin/sudo virsh --connect qemu:///system console --force b.east
> 4 0 27803 27801 20 0 318584 13924 - Sl+ pts/11 0:01 | | | \_ virsh --connect qemu:///system console --force b.east
> 4 0 27950 21405 20 0 232176 10132 - Ss+ pts/4 0:00 | | \_ /usr/bin/sudo virsh --connect qemu:///system console --force a.west
> 4 0 27952 27950 20 0 318584 16640 - Sl+ pts/4 0:00 | | | \_ virsh --connect qemu:///system console --force a.west
> 4 0 27954 21405 20 0 232176 10108 - Ss+ pts/8 0:00 | | \_ /usr/bin/sudo virsh --connect qemu:///system console --force a.east
> 4 0 27956 27954 20 0 318584 16740 - Sl+ pts/8 0:00 | | | \_ virsh --connect qemu:///system console --force a.east
> 4 0 27978 21405 20 0 0 0 - Zs ? 0:00 | | \_ [sudo] <defunct>
>
> The only thing that looks suspicious to me is the last line. Why isn't the sudo process being reaped?
>
> I'll leave the hung test run for a bit in case someone can help me investigate this.
> _______________________________________________
> Swan-dev mailing list
> Swan-dev at lists.libreswan.org
> https://lists.libreswan.org/mailman/listinfo/swan-dev
More information about the Swan-dev
mailing list