On 05 Jun 2020 19:02, Petter Reinholdtsen wrote:
>
> I discovered what the problem is. The test [ $res ] do not work the way
> you want it to. It need to compare with 0, like this:
Which is kind of strange, and makes autopkgtest very hard to use since
this works fine when run locally like so:
I discovered what the problem is. The test [ $res ] do not work the way
you want it to. It need to compare with 0, like this:
diff --git a/debian/tests/test01 b/debian/tests/test01
index 1c0d63f..73e1fac 100755
--- a/debian/tests/test01
+++ b/debian/tests/test01
@@ -1,4 +1,5 @@
#!/bin/sh
+
[Al Stone]
> Hrm. So write access seems to be more constrained than this led
> me to believe; I'll try these patches out and rebuild tonight. I
> did think about using AUTOPKGTEST_TMP but had not convinced myself
> it was absolutely required.
Note, I am not convinced this will help, as I am
On 03 Jun 2020 14:30, Petter Reinholdtsen wrote:
>
> Could
> https://people.debian.org/~mpitt/autopkgtest/README.package-tests.html >
> contain the key to why these test are failing? It states
>
> "The cwd of each test is guaranteed to be the root of the source
> package, which will have
Could
https://people.debian.org/~mpitt/autopkgtest/README.package-tests.html >
contain the key to why these test are failing? It states
"The cwd of each test is guaranteed to be the root of the source
package, which will have been unpacked but not built. However note
that the tests must
Package: gnucobol
Version: 3.0~rc1-2
Severity: serious
Tags: patch
Several of the automatic tests provided in debian/tests/ currently fail.
I am unable to see from the logs what go wrong, but the failure block
the package from migrating into testing. When I run the scripts
locally, they work.
6 matches
Mail list logo
