DEP8 test failed with output on stderr
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
oneconf (Ubuntu) |
Fix Released
|
Undecided
|
Barry Warsaw |
Bug Description
autopkgtest for oneconf failed with there is output to stderr:
"""
+ python3 setup.py nosetests -vv --test test.test_
/usr/lib/
warnings.
.......
-------
Ran 22 tests in 0.324s
OK
+ python3 setup.py nosetests -vv --test test.test_syncing
/usr/lib/
warnings.
.......
-------
Ran 29 tests in 441.769s
OK
+ xvfb-run python3 setup.py nosetests -vv --test test.test_daemon
"""
According do DEP8 specification [1]
"Each test program should, on success, exit with status 0 and print nothing to stderr; if a test exits nonzero, or prints to stderr, it is considered to have failed."
The 2 problems are:
1. debian/
2. output stream is stderr
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: oneconf 0.3
ProcVersionSign
Uname: Linux 3.8.0-1-generic x86_64
ApportVersion: 2.8-0ubuntu2
Architecture: amd64
Date: Tue Jan 22 10:03:59 2013
MarkForUpload: True
PackageArchitec
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: oneconf
UpgradeStatus: Upgraded to raring on 2012-01-31 (356 days ago)
description: | updated |
Oops. -x was a debugging artifact. I'm currently having some trouble running autopkgtests locally, but I'll remove the -x on the next upload.