Hello, Matthias Klose [2014-01-13 3:02 +0100]: > This test is failing this is was introduced in 2012.10.24-6. However the log > doesn't tell what exactly is failing. > > - afaics the test is at least missing a dependency on aspcud > - sending all output to /dev/null is a bad idea for an untested > test script.
Attached patch at least fixes those, and the wrong $indir directory (autopkgtests are run from the source tree root). Please don't do "2>/dev/null". If your test always writes expected stuff to stderr, then add "Restrictions: allow-stderr" to debian/tests/control. Otherwise, if the test is not supposed to write to stderr, don't redirect it (preferrable to detect unexpected regressions/warnings/etc.) But now further errors appear: | $ TMPDIR=/tmp/x sh -x debian/tests/upstream | + set -e | + indir=debian/tests/cudf | + outdir=/tmp/x | + basename debian/tests/cudf/feature.cudf | + cudf=feature.cudf | + outfile=/tmp/x/feature.sol | + checkfile=/tmp/x/feature.check | + aspcud debian/tests/cudf/feature.cudf /tmp/x/feature.sol trendy | *** ERROR: (clasp): Read Error: Line 0, Bad input stream! | | /usr/share/aspcud/encodings/misc2012.lp:46:45-46: error: syntax error, unexpected : | | /usr/share/aspcud/encodings/misc2012.lp:74:2: error: lexer error, unexpected # | | /usr/share/aspcud/encodings/misc2012.lp:90:44-45: error: syntax error, unexpected : | | /usr/share/aspcud/encodings/misc2012.lp:91:44-45: error: syntax error, unexpected : | | /usr/share/aspcud/encodings/misc2012.lp:138:38-39: error: syntax error, unexpected : | | /usr/share/aspcud/encodings/misc2012.lp:144:38-39: error: syntax error, unexpected : | | /usr/share/aspcud/encodings/misc2012.lp:146:38-39: error: syntax error, unexpected : | | /usr/share/aspcud/encodings/misc2012.lp:148:38-39: error: syntax error, unexpected : | | /usr/share/aspcud/encodings/misc2012.lp:150:38-39: error: syntax error, unexpected : | | /usr/share/aspcud/encodings/misc2012.lp:197:39-40: error: syntax error, unexpected : | | /usr/share/aspcud/encodings/misc2012.lp:200:35-36: error: syntax error, unexpected : | | /usr/share/aspcud/encodings/misc2012.lp:202:35-36: error: syntax error, unexpected : | | /usr/share/aspcud/encodings/misc2012.lp:221:64-65: error: syntax error, unexpected :, expecting . or ; | | /usr/share/aspcud/encodings/misc2012.lp:223:64-65: error: syntax error, unexpected :, expecting . or ; | | /usr/share/aspcud/encodings/misc2012.lp:235:35-36: error: syntax error, unexpected : | | /usr/share/aspcud/encodings/misc2012.lp:259:39-40: error: syntax error, unexpected : | | /usr/share/aspcud/encodings/misc2012.lp:306:73-74: error: syntax error, unexpected :, expecting . or ; | | /usr/share/aspcud/encodings/misc2012.lp:330:49-50: error: syntax error, unexpected :, expecting . or ; | | /usr/share/aspcud/encodings/misc2012.lp:336:52-53: error: syntax error, unexpected :, expecting . or ; | | /usr/share/aspcud/encodings/misc2012.lp:375:56-57: error: syntax error, unexpected :, expecting . or ; | | | Exception: too many messages. | + cudf-check -cudf debian/tests/cudf/feature.cudf -sol /tmp/x/feature.sol So the main problem seems to be the "bad input stream", but I have no idea about that. > so please set TMPDIR. autopkgtest does that, but for manually running the test it's indeed more convenient to just use something /tmp/aspcud-test if $TMPDIR is unset. Thanks, Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
--- aspcud-1.8.0/debian/tests/control 2014-01-11 09:27:53.000000000 +0100
+++ aspcud-1.8.0.new/debian/tests/control 2014-01-13 07:26:51.322461599 +0100
@@ -1,2 +1,2 @@
Tests: upstream
-Depends: cudf-tools
+Depends: @, cudf-tools
--- aspcud-1.8.0/debian/tests/upstream 2014-01-11 09:27:53.000000000 +0100
+++ aspcud-1.8.0.new/debian/tests/upstream 2014-01-13 07:31:37.990461599 +0100
@@ -2,7 +2,7 @@
set -e
-indir=cudf
+indir=debian/tests/cudf
outdir=$TMPDIR
for infile in $indir/*.cudf
@@ -10,8 +10,8 @@
cudf=$(basename $infile)
outfile=$outdir/${cudf%.cudf}.sol
checkfile=$outdir/${cudf%.cudf}.check
- aspcud $infile $outfile trendy > /dev/null 2>&1
- cudf-check -cudf $infile -sol $outfile > $checkfile 2> /dev/null
+ aspcud $infile $outfile trendy
+ cudf-check -cudf $infile -sol $outfile > $checkfile
if [ `grep -c "is_solution: true" $checkfile` -ne 1 ]
then
echo "Test \"legacy\" with options \"$solver\":"
signature.asc
Description: Digital signature
