Bug#726983: visp: autopkgtest failure due to stderr output from test program

Martin Pitt martin.pitt at ubuntu.com
Mon Oct 21 09:01:58 UTC 2013


Package: visp
Version: 2.8.0-2
Tags: patch
User: ubuntu-devel at lists.ubuntu.com
Usertags: origin-ubuntu ubuntu-patch trusty

Hello,

Running visp's autopkgtest currently fails [1]:

| adt-run: & dsc0t-build: [----------------------------------------
| adt-run1: teeing to stdout: /tmp/adt-run.kkup5e/dsc0t-build-testtmp/test_stdout, stderr: /tmp/adt-run.kkup5e/dsc0t-build-testtmp/test_stderr
| build: OK
| libdc1394 error: Failed to initialize libdc1394
| run: OK
| adt-run1: testbed executing test finished with exit status 0
| adt-run: & dsc0t-build: ----------------------------------------]
| adt-run: & dsc0t-build:  - - - - - - - - - - results - - - - - - - - - -
| dsc0t-build          FAIL status: 0, stderr: libdc1394 error: Failed to initialize libdc1394
| adt-run: & dsc0t-build:  - - - - - - - - - - stderr - - - - - - - - - -
| libdc1394 error: Failed to initialize libdc1394

Apparently the library has some constructor which prints that error
message on machines without firewire. That's usually the case for VMs
or servers where autopkgtests are being run.

I don't want to suppress stderr for the entire debian/tests/build as
gcc or other bits could produce some unexpected errors. So in the
Ubuntu fix I only re-route the test program's stderr to stdout, which
fixes the test.

Thanks for considering,

Martin

[1] https://jenkins.qa.ubuntu.com/job/trusty-adt-visp/1
-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
-------------- next part --------------
diff -Nru visp-2.8.0/debian/changelog visp-2.8.0/debian/changelog
--- visp-2.8.0/debian/changelog	2013-09-13 04:23:37.000000000 +0200
+++ visp-2.8.0/debian/changelog	2013-10-21 10:55:42.000000000 +0200
@@ -1,3 +1,11 @@
+visp (2.8.0-2ubuntu1) trusty; urgency=low
+
+  * debian/tests/build: Route stderr from built test program to stdout, so that
+    the "libdc1394 error: Failed to initialize libdc1394" message doesn't
+    fail the test.
+
+ -- Martin Pitt <martin.pitt at ubuntu.com>  Mon, 21 Oct 2013 10:54:56 +0200
+
 visp (2.8.0-2) unstable; urgency=low
 
   * debian/control: libvisp2.8 breaks+replaces libvisp2 (Closes: #722647).
diff -Nru visp-2.8.0/debian/tests/build visp-2.8.0/debian/tests/build
--- visp-2.8.0/debian/tests/build	2013-06-18 16:42:45.000000000 +0200
+++ visp-2.8.0/debian/tests/build	2013-10-21 10:54:27.000000000 +0200
@@ -22,5 +22,7 @@
 g++ -o visptest visptest.cpp `pkg-config --cflags --libs visp`
 echo "build: OK"
 [ -x visptest ]
-./visptest
+# often prints "libdc1394 error: Failed to initialize libdc1394" to stderr,
+# avoid test failure due to that
+./visptest 2>&1
 echo "run: OK"


More information about the debian-science-maintainers mailing list