Right, no need to further debug timeout/adt-run bad interactions indeed.
The initial need was to make sure adt-run will always timeout. If we
have a way to do that while all missing timeouts are added to adt-run
(if some are still missing...), we're good.
--
You received this bug notification be
** Changed in: autopkgtest (Ubuntu)
Status: New => Triaged
** Changed in: autopkgtest (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1415944
Title:
ad
Simple reproducer is this command:
$ sh -c 'timeout 600 adt-run -d libpng --- qemu /srv/vm/adt-vivid-
amd64-cloud.img'
whereas
$ timeout 600 adt-run -d libpng --- qemu /srv/vm/adt-vivid-
amd64-cloud.img
works fine. So interactive shells have a different TTY and/or signal
setup than noninteracti
Note: Running "timeout --foreground 600 adt-run ..." works as well; that
might not be precisely what you're after, though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1415944
Title:
adt-run gets s
