On Thu, 2013-07-25 at 13:34 +0200, Martin Pitt wrote:
> saucy-adt-ubuntuone-client (supposed to work now, problem with "allow-stderr")
This just requires a new upload, to add the allow-stderr flag, if one
been done already. I haven't had time to do it as I've had higher
work at the moment. I can probably get to this early next week.
> saucy-adt-software-center (never worked)
These apparently never worked, and instead of constantly uploading new
that simply removes the newly failing tests, I decided it's best to just
the autopkgtest config, as it never worked. This should have been
jenkins by now as well, as I alerted you on IRC that I was doing this.
> == uploaded by particular developer ==
> saucy-adt-dirspec (never worked, dobey)
I'm guessing this is the python unit tests printing stuff to stderr
The tests are passing, but adt-run is failing anyway.
For the stderr case, it would be helpful if adt-run also printed
to stderr itself, stating the tests failed for that reason. This is all
I see in the
"console output" on jenkins, and it's not very helpful to know what
wrong (without external context/knowledge):
adt-run: trace: & dsc0t-run-tests:
adt-run: trace1: ** needs_reset, previously=False
adt-run: trace: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ tests done.
adt-run: trace: ** stop
adt-run: trace: ** close, scratch=tb-scratch~/tmp/tmp.f4r1xGFccn:-/|/tmp/tmp.f4r1xGFccn/!
Connection to localhost closed.
2013-07-12 15:01:43: Failure: adt-run exited with status 4.
ubuntu-devel mailing list
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel