Hello Ralf, Ralf Treinen [2014-01-13 16:53 +0100]: > thanks for your patch. However, I cannot reproduce that Bad Input Stream > error on my machine. What are the versions of the dependencies of aspcud > that you had installed when running this test ?
Indeed I re-tried in sid, and that particular "Bad Input Stream" error doesn't happen there: /tmp/aspcud-1.8.0 $ adt-run -B .// --- adt-virt-schroot sid [...] adt-run: & ubtree0t-upstream: - - - - - - - - - - results - - - - - - - - - - ubtree0t-upstream FAIL non-zero exit status 126 adt-run: & ubtree0t-upstream: - - - - - - - - - - stderr - - - - - - - - - - /usr/bin/aspcud: /tmp/adt-run.rFHKC6/ubtree0t-upstream-testtmp/tmpdir/outNJPr7x/parse.py: /usr/bin/python: bad interpreter: No such file or directory So apparently something in these tests uses python, but python isn't a dependency of the package or the tests. Once I add that, the test merely fails on some stderr output, but with the "allow-stderr" restriction above command now succeeds for me. debian/tests/control now: ------------ 8< ------------ Tests: upstream Depends: @, cudf-tools, python Restrictions: allow-stderr ------------ 8< ------------ It may very well be that "python" actually needs to be a binary dependency of aspcud or cudf-tools, I didn't check that closely. So, I don't know what's different in Ubuntu trusty at the moment. We have the exact same versions of aspcud, cudf-tools, gringo, and clasp as in sid, just some slightly different gcc versions. I'll investigate this more closely on the Ubuntu side tomorrow. For now, the previously attached patch and above python/allow-stderr adjustments should suffice for Debian. Thanks! Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
