On 2018-10-17 21:28, Emilio G. Cota wrote: > On Thu, Oct 11, 2018 at 20:25:08 +0100, Dr. David Alan Gilbert (git) wrote: >> From: Thomas Huth <th...@redhat.com> >> >> We can re-use the s390-ccw bios code to implement a small firmware >> for a s390x guest which prints out the "A" and "B" characters and >> modifies the memory, as required for the migration test. >> >> [quintela: Converted the compile script to Makefile rules] >> Signed-off-by: Juan Quintela <quint...@redhat.com> >> Signed-off-by: Thomas Huth <th...@redhat.com> >> Message-Id: <1539078677-25396-1-git-send-email-th...@redhat.com> >> Reviewed-by: Philippe Mathieu-Daudé <phi...@redhat.com> >> Tested-by: Philippe Mathieu-Daudé <phi...@redhat.com> >> Signed-off-by: Dr. David Alan Gilbert <dgilb...@redhat.com> >> Fixed up Makefile since the aarch patch sneaked in first > > I suspect this test is giving me intermittent hangs. I've seen the hangs > in different machines, but when they're lightly loaded the > hang happens more frequently. > > To reproduce: > > $ ./configure --target-list=s390x-softmmu > $ make clean && make > $ for i in $(seq 0 150); do echo $i && make -j check-qtest || break; done > > It usually ends up hanging before 50 runs. When the hang happens, I see > two qemu-system-s390x processes with: > > -serial file:/tmp/migration-test-0FZErQ/dest_serial > > as an argument, among others. That means the migration test is the > one hanging, correct?
Can you also reproduce it directly by only running the migration test alone, just to be sure? I.e. run something like this in a loop: QTEST_QEMU_BINARY="s390x-softmmu/qemu-system-s390x" tests/migration-test Thanks, Thomas
