Your message dated Sun, 3 Jan 2016 16:11:36 +0100
with message-id <[email protected]>
and subject line Re: Bug#809661: debci: Should not assume that output to stderr
means FAILED
has caused the Debian Bug report #809661,
regarding debci: Should not assume that output to stderr means FAILED
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
809661: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809661
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: debci
Version: 1.0.1
Severity: important
Dear debci people,
debci should monitor return codes of the test scripts to determine failure.
Analyzing if there is something spitted out to stderr will cause false
positives.
Example is package log4cxx.
Here, a autoconf warning "configure.in is depreciated" will cause ci.debian.net
to claim failure,
down the road a testcase which is *expected* to print an error fails, failing
the whole check.
(I'm currently preparing an upload with an workaround by redirecting sterr to
stdout)
Minimized testcase:
build-tests containing:
#!/bin/sh
echo "Everythings cool, stderr!" 1>&2
will yield to:
tobi@edoras:~/workspace/deb/packages/log4cxx/log4cxx$ adt-run --output-dir
/tmp/output-dir8 ./ --- null
adt-run [15:03:09]: version 3.19
adt-run [15:03:09]: host edoras; command line: /usr/bin/adt-run --output-dir
/tmp/output-dir8 ./ --- null
adt-run [15:03:09]: testbed dpkg architecture: amd64
adt-run [15:03:09]: testbed running kernel: Linux 4.3.0-1-amd64 #1 SMP Debian
4.3.3-2 (2015-12-17)
adt-run [15:03:09]: @@@@@@@@@@@@@@@@@@@@ built-tree ./
adt-run [15:03:09]: testing package dummy version 0-1
adt-run [15:03:10]: test build-tests: preparing testbed
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
adt-run [15:03:11]: test build-tests: [-----------------------
Everythings cool, stderr!
adt-run [15:03:11]: test build-tests: -----------------------]
adt-run [15:03:12]: test build-tests: - - - - - - - - - - results - - - - - -
- - - -
build-tests FAIL stderr: Everythings cool, stderr!
adt-run [15:03:12]: test build-tests: - - - - - - - - - - stderr - - - - - - -
- - -
Everythings cool, stderr!
adt-run [15:03:12]: @@@@@@@@@@@@@@@@@@@@ summary
build-tests FAIL stderr: Everythings cool, stderr!
--
tobi
-- System Information:
Debian Release: stretch/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages debci depends on:
ii adduser 3.113+nmu3
ii amqp-tools 0.7.1-1
ii bsdmainutils 9.0.6+b1
ii dctrl-tools 2.24-1
ii debootstrap 1.0.75
ii devscripts 2.15.9
ii fonts-font-awesome 4.4.0~dfsg-1
ii libjs-bootstrap 3.3.6+dfsg-1
ii libjs-jquery 1.11.3+dfsg-4
ii libjs-jquery-flot 0.8.3+dfsg-1
ii patchutils 0.3.4-1
ii ruby 1:2.2.4
ii sudo 1.8.12-1
Versions of packages debci recommends:
pn apt-cacher-ng <none>
ii moreutils 0.57-1
ii ntp 1:4.2.8p4+dfsg-3+b1
debci suggests no packages.
-- Configuration Files:
/etc/sudoers.d/debci [Errno 13] Keine Berechtigung: u'/etc/sudoers.d/debci'
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello Tobias,
Tobias Frost [2016-01-02 15:04 +0100]:
> debci should monitor return codes of the test scripts to determine failure.
> Analyzing if there is something spitted out to stderr will cause false
> positives.
This is autopkgtest (i. e. adt-run), not debci itself. debci only
evaluates adt-run's exit code.
By default, autopkgtest scripts must exit with 0 *and* not spit out
anything on stderr in order to be considered "success". You can
disable failing on stderr with "Restrictions: allow-stderr". Please
see /usr/share/doc/autopkgtest/README.package-tests.html aka
https://people.debian.org/~mpitt/autopkgtest/README.package-tests.html
This has been the defined behaviour for a decade and is rather useful
to spot things like newly appearing, but unexpected warnings, so it
won't be changed.
Thanks,
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
--- End Message ---
