The test history indicates this might be due to some golang changes and indeed the entry point to the test is /usr/bin/dh_golang_autopkgtest.
While autopkgtest says:
autopkgtest [10:12:21]: test command1: preparing testbed
as usual.
There actually is no debian/test* at all, so this must be something go-special that I haven't encountered yet.
# rerun tests
$ cd /tmp/autopkgtest.v7GzBZ/build.EOf/src
$ mkdir /tmp/autopkgtest.v7GzBZ/autopkgtest_tmp2
$ export AUTOPKGTEST_TMP=/tmp/autopkgtest.v7GzBZ/autopkgtest_tmp2
...
leads to the same breakage as we see in the autopkgtest running on the infrastructure
The test history indicates this might be due to some golang changes and indeed the entry point to the test is /usr/bin/ dh_golang_ autopkgtest.
While autopkgtest says:
autopkgtest [10:12:21]: test command1: preparing testbed
as usual.
There actually is no debian/test* at all, so this must be something go-special that I haven't encountered yet.
# rerun tests t.v7GzBZ/ build.EOf/ src t.v7GzBZ/ autopkgtest_ tmp2 TMP=/tmp/ autopkgtest. v7GzBZ/ autopkgtest_ tmp2
$ cd /tmp/autopkgtes
$ mkdir /tmp/autopkgtes
$ export AUTOPKGTEST_
...
leads to the same breakage as we see in the autopkgtest running on the infrastructure