DEP8 test failed with output on stderr

Bug #1102875 reported by Jean-Baptiste Lallement on 2013-01-22
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
oneconf (Ubuntu)
Undecided
Barry Warsaw

Bug Description

autopkgtest for oneconf failed with there is output to stderr:
"""
+ python3 setup.py nosetests -vv --test test.test_mainfeatures
/usr/lib/python3.3/distutils/dist.py:257: UserWarning: Unknown distribution option: 'test_requires'
  warnings.warn(msg)
......................
----------------------------------------------------------------------
Ran 22 tests in 0.324s

OK
+ python3 setup.py nosetests -vv --test test.test_syncing
/usr/lib/python3.3/distutils/dist.py:257: UserWarning: Unknown distribution option: 'test_requires'
  warnings.warn(msg)
.............................
----------------------------------------------------------------------
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/tests/unittests is executed with -x
2. output stream is stderr

[1] http://anonscm.debian.org/gitweb/?p=autopkgtest/autopkgtest.git;a=blob_plain;f=doc/README.package-tests;hb=HEAD

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: oneconf 0.3
ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
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
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: oneconf
UpgradeStatus: Upgraded to raring on 2012-01-31 (356 days ago)

Jean-Baptiste Lallement (jibel) wrote :
description: updated
Barry Warsaw (barry) wrote :

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.

Changed in oneconf (Ubuntu):
assignee: nobody → Barry Warsaw (barry)
status: New → In Progress
Barry Warsaw (barry) wrote :

Hmm, I guess -vv needs to be removed and -q added to get quiet output. I don't see a way to ask nose to output to stdout instead of stderr (which I think is the default). That's rather unhelpful in the case of failures, but maybe it's not so bad for several reasons, among them that I think you'll get test failure output, and besides the same tests are already run at build time and this is just a sanity check.

Barry Warsaw (barry) wrote :

The lp:auto-package-testing branch is not working for me today (due to LP: #1103739), so I can't completely test this locally. Uploaded 0.3.3 which should fix the problem but let me know if it doesn't.

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package oneconf - 0.3.3

---------------
oneconf (0.3.3) raring; urgency=low

  * d/tests/unittests: Remove -x debugging artifact and run the nose tests
    under -q instead of -vv to inhibit stderr output. (LP: #1102875)
  * oneconf-query: Use gettext.install() to install the _() function.
    (LP: #1103192)
 -- Barry Warsaw <email address hidden> Wed, 23 Jan 2013 18:30:05 -0500

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

Other bug subscribers