Bug#680473: dep8 test failed with message on stderr
2 views
Skip to first unread message
Jean-Baptiste Lallement
unread,
Jul 6, 2012, 4:00:02 AM7/6/12
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to
Package: tabix
Version: 0.2.6-1
autopkgtest of tabix [1] currently fails with:
"""
adt-run: trace: & dsc0t-with-example-data: - - - - - - - - - - results
- - - - - - - - - -
dsc0t-with-example-data FAIL status: 0, stderr: [tabix] The file type
not recognise...
adt-run: trace: & dsc0t-with-example-data: - - - - - - - - - - stderr -
- - - - - - - - -
[tabix] The file type not recognised and -p not given, using the preset
[gff].
adt-run: trace: & dsc0t-with-example-data:
----------------------------------------]
"""
This is because the warning is written to stderr while per specification
of DEP8 it should be written to stdout.
Excerpt from from DEP8 specification [2]
"""
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 dep8 test should be updated either to use the option -p of tabix to
fix the warning/error or redirect stderr to stdout and exit with an
appropriate exit code if the message is expected.
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to
tag 680473 pending
thanks
Le Fri, Jul 06, 2012 at 09:39:08AM +0200, Jean-Baptiste Lallement a écrit :
>
> The dep8 test should be updated either to use the option -p of tabix
> to fix the warning/error or redirect stderr to stdout and exit with
> an appropriate exit code if the message is expected.
Dear Jean-Baptiste,
thanks for the detailed report. I committed the correction in the source
package's Git repository. Tabix releases are infrequent so it may take time
before the bug is really closed. If you need to get this done before the next
upstream release, please let me know.