[Bug 1415944] Re: adt-virt-qemu hang

[Martin Pitt]

If I drop the "timeout" bit from $ADT_CMD, it works fine as well. When
prepending the timeout call in boottest.sh with strace -vvtts1024 -o
/tmp/tr, I get

18:07:16.733950 clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7f11825c3a10) = 26085
18:07:16.734086 rt_sigprocmask(SIG_UNBLOCK, [ALRM], NULL, 8) = 0
18:07:16.734154 timer_create(CLOCK_REALTIME, {0x2518030, SIGALRM, SIGEV_SIGNAL, {...}}, {0}) = 0
18:07:16.734209 timer_settime(0, 0, {it_interval={0, 0}, it_value={600, 0}}, NULL) = 0
18:07:16.734260 wait4(26085, 0x7fffad6743dc, 0, NULL) = ? ERESTARTSYS (To be restarted if SA_RESTART is set)
18:07:35.411480 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_STOPPED, si_pid=26085, si_status=SIGTTIN, si_utime=11, si_stime=1} ---
18:07:35.411537 --- SIGTTIN {si_signo=SIGTTIN, si_code=SI_KERNEL, si_value={int=21, ptr=0x15}} ---
18:07:35.411602 wait4(26085, 

At that time (18:07:35.) all the child processes get stopped.

This isn't specific to qemu, it also happens with the LXC runner.

** Summary changed:

- adt-virt-qemu hang
+ adt-run gets stopped when running under timeout

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to autopkgtest in Ubuntu.
https://bugs.launchpad.net/bugs/1415944

Title:
  adt-run gets stopped when running under timeout

Status in autopkgtest package in Ubuntu:
  New

Bug description:
   $ mkdir tmp
   $ adt-buildvm-ubuntu-cloud -v -r vivid
   $ bzr branch lp:~canonical-ci-engineering/ubuntu-test-cases/boottest
  $ export ADT_VIRT="adt-virt-qemu ./adt-vivid-amd64-cloud.img"
  $ boottest/scripts/boottest.sh vivid libpng

  This ends with:

  adt-run [15:40:11]: version 3.9.3-1~1034~ubuntu14.04.1
  adt-run: DBG: $ vserver: adt-virt-qemu /home/vila/ci/adt-vivid-amd64-cloud.img
  adt-run: DBG: got reply from testbed: ok
  adt-run: DBG: testbed open, scratch=None
  adt-run: DBG: sending command to testbed: open
  adt-run: DBG: got reply from testbed: ok /tmp/adt-run.dKQGkT
  adt-run: DBG: sending command to testbed: print-execute-command
  adt-run: DBG: got reply from testbed: ok /tmp/adt-virt-qemu.wuid9js5/runcmd
  adt-run: DBG: sending command to testbed: capabilities
  adt-run: DBG: got reply from testbed: ok revert revert-full-system root-on-testbed isolation-machine reboot suggested-normal-user=ubuntu
  adt-run: DBG: testbed capabilities: ['revert', 'revert-full-system', 'root-on-testbed', 'isolation-machine', 'reboot', 'suggested-normal-user=ubuntu']
  adt-run [15:40:30]: @@@@@@@@@@@@@@@@@@@@ test bed setup
  adt-run: DBG: testbed command ['sh', '-ec', 'awk \'/^deb(-src)? .*(ubuntu.com|debian.org|ftpmaster)/ { if ($3 !~ /-/) { $3 = $3"-proposed"; print }}\' /etc/apt/sources.list `ls /etc/apt/sources.list.d/*.list 2>/dev/null|| true`  > /etc/apt/sources.list.d/proposed.list'], kind short, sout raw, serr pipe, env ['LANG=C.UTF-8']

  The boottest.sh scripts includes a 'timeout 600 adt-run ..." and
  everything gets killed properly after hanging on the above.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1415944/+subscriptions