adt-run broken except when used with adt-virt-null
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
autopkgtest (Ubuntu) |
Fix Released
|
High
|
Martin Pitt |
Bug Description
2.3.6 does, in adt-run:run:
os.mkfifo(fifo_out) (and fifo_err)
fifo_out uses the testtmp path.
testtmp is created above that, in the guest.
But os.mkfifo runs in the host.
This causes the traceback:
adt-run: unexpected, exceptional, error:
Traceback (most recent call last):
File "/usr/bin/adt-run", line 2205, in main
process_
File "/usr/bin/adt-run", line 2177, in process_actions
run_
File "/usr/bin/adt-run", line 1315, in run_tests
t.run(tree)
File "/usr/bin/adt-run", line 1428, in run
os.
OSError: [Errno 2] No such file or directory
This is with adt-virt-lxc (which has yet to land), but I believe it will do it with anything but adt-virt-null.
Version 2.3.3 is not affected.
Related branches
Changed in autopkgtest (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Martin Pitt (pitti) |
milestone: | none → ubuntu-13.10 |
status: | Triaged → In Progress |
Reproduced in a new test case which exercises the chroot runner, and fixed in git.