[Bug 888910] Re: "make check" fails in sbuild chroot

[Jamie Strandboge]

The ubuntu security team has standardized on sbuild and all of our tools
use it. We do this because we want to closely mimic the official
buildds, which use sbuild (though an older one that seemingly has some
sort of workaround for upstart).

My workaround wasn't meant to be run unconditionally, but instead to
document how one could build a package locally with sbuild after
noticing the initial build failed. This is needed for local testing.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/888910

Title:
  "make check" fails in sbuild chroot

Status in Upstart:
  Fix Committed
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  As reported to upstart-devel mailing list by broder, "make check"
  fails in an sbuild chroot:

   test_job_process: tests/test_job_process.c:3726: test_handler:
  Assertion `(waitid (P_PID, pid, &info, 2 | 0x01000000)) == 0' failed.
   /bin/bash: line 5: 27647 Aborted                 (core dumped) ${dir}$tst
   FAIL: test_job_process

  Evan also found the cause:

    http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607844

  Upstarts tests should detect and handle this situation by checking
  ttyname(3) and taking appropriate action. It should also log a warning
  if action is required.

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/888910/+subscriptions