autopkgtest'ing against multiple Python versions

Jakub Wilk jwilk at
Mon Apr 23 14:30:25 UTC 2012

* Yaroslav Halchenko <debian at>, 2012-04-23, 09:17:
>>The “failures” was caused by the following misfeature of the 
>>specification: “if a test […] prints to stderr, it is considered to 
>>have failed.” But nosetests does print stuff to stderr even if 
>>everything is all right (see bug #460242).
>yikes -- doesn't it fail if underlying "test command" returns with 
>non-0 exit code?

Thankfully it does. :)
s/[…]/exits nonzero, or/ - sorry for the confusion.

>IMHO that should be the criterion, not catching stderr, which might 
>have some spurious output from tests which might be testing either 
>application handles erroneous cases correctly (where it might output to 

ACK. Even if nosetests printed the usual stuff to stdout, I would still 
have to redirect stderr to stdout (or /dev/null), because the tested 
code could rightfully emit warnings.

Jakub Wilk

More information about the autopkgtest-devel mailing list