[Bug 1235189] Re: adt-run broken except when used with adt-virt-null

[Martin Pitt]

** Changed in: autopkgtest (Ubuntu)
       Status: New => Triaged

** Changed in: autopkgtest (Ubuntu)
   Importance: Undecided => High

** Changed in: autopkgtest (Ubuntu)
     Assignee: (unassigned) => Martin Pitt (pitti)

** Changed in: autopkgtest (Ubuntu)
    Milestone: None => ubuntu-13.10

** Changed in: autopkgtest (Ubuntu)
       Status: Triaged => In Progress

-- 
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/1235189

Title:
  adt-run broken except when used with adt-virt-null

Status in “autopkgtest” package in Ubuntu:
  In Progress

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_actions()
    File "/usr/bin/adt-run", line 2177, in process_actions
      run_tests(stanzas, act.tests_tree)
    File "/usr/bin/adt-run", line 1315, in run_tests
      t.run(tree)
    File "/usr/bin/adt-run", line 1428, in run
      os.mkfifo(fifo_out)
  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.

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