[Bug 1463561] Re: adt-run eats its log dir for breakfast

[Launchpad Bug Tracker]

This bug was fixed in the package autopkgtest - 3.15.1

---------------
autopkgtest (3.15.1) unstable; urgency=medium

  * adt-buildvm-ubuntu-cloud: Fix lsb_release fallback if python3-distro-info
    is not available.
  * adt-buildvm-ubuntu-cloud: Don't move the uninitialized image to final
    location if QEMU failed.
  * adt-buildvm-ubuntu-cloud: Check availability of genisoimage and access of
    /dev/kvm before downloading image. (LP: #1466486)
  * Get along with dpkg-query not existing, such as in latest Ubuntu Snappy
    images. Skip generation of testbed-packages artifact in that case.
    (LP: #1469647)
  * Adjust NullRunner.test_tmp_install test case to work with pygobject 3.16.

 -- Martin Pitt <martin.pitt at ubuntu.com>  Mon, 29 Jun 2015 13:07:34
+0200

** Changed in: autopkgtest (Ubuntu)
       Status: Fix Committed => Fix Released

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

Title:
  adt-run eats its log dir for breakfast

Status in autopkgtest package in Ubuntu:
  Fix Released

Bug description:
  Before running any tests, adt-run does a 'rm -rf' of its log
  directory, and aborts if this causes any errors.

  This is a problem because it's dangerous, it's unintuitive, and it
  breaks unix conventions.

  Dangerous:  Ever tried using $HOME as the log dir?  When an attempt to
  use /tmp for logging fails due to permission issues, the next obvious
  choice is to use '.' or $HOME, which can cause disaster.

  Unintuitive: The obvious first choices for a log dir are places like
  /tmp, ., $HOME, and /var/log.  None of these actually work, and fail
  with a traceback.  It's awkward to require a directory which doesn't
  even exist.

  Breaks conventions: In general, most tools want to have a parent
  directory or an existing directory specified for their logging, as in
  the list of common directories above.  Then the convention-compliant
  tool either writes logs to that directory (without first 'rm -rf'ing
  it) or creates a new child subdirectory such as /tmp/foo.24153/ to
  store results in.  adt-run does not do this, which creates surprising
  results.

  Could we change the log dir behavior of adt-run to be safer and more
  similar to other tools?

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