ssh failure should cause testbed error code

Bug #1462540 reported by Martin Pitt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
autopkgtest (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

http://d-jenkins.ubuntu-ci:8080/job/wily-boottest-telepathy-ofono/3/artifact/results/log/*view*/ failed in apt-get source with

adt-run: DBG: testbed command exited with code 255
blame: /var/lib/jenkins/slaves/krillin-09/workspace/wily-boottest-telepathy-ofono/test-runner/scripts/../tests/boottest
badpkg: rules extract failed with exit code 255
adt-run [20:57:15]: ERROR: erroneous package: rules extract failed with exit code 255

But Pauls says the entire adt-run exited with 12 then ("erroneous package"), but it should be 16 (testbed failure).

Martin Pitt (pitti)
Changed in autopkgtest (Ubuntu):
importance: Undecided → Medium
assignee: nobody → Martin Pitt (pitti)
status: New → Triaged
Revision history for this message
Martin Pitt (pitti) wrote :
Changed in autopkgtest (Ubuntu):
assignee: Martin Pitt (pitti) → nobody
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package autopkgtest - 3.14.3

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

  * adt-virt-lxc: Don't try to set up a shared downtmp with unprivileged
    (user) containers. This is full of permission errors due to the mapped
    UIDs.
  * tests/adt-run LxcRunner: Use $ADT_TEST_LXC as unprivileged user container
    if it exists.
  * adt-buildvm-ubuntu-cloud: Check at the beginning if QEMU command is
    available and exit with proper error message if not. (LP: #1460066)
  * If auxverb fails with exit code 126, 127, 254, or 255, consider this a
    failure of auxverb/the testbed itself, not of the program run under it.
    (As specified in doc/README.virtualisation-server.rst) (LP: #1462540)

 -- Martin Pitt <email address hidden> Sat, 06 Jun 2015 13:09:50 +0200

Changed in autopkgtest (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.