Mysterious autopkgtest tests of ujson package
Hello mentors,
I'm adopting the ujson package[1][2]. Currently there is no autopkgtest
control file under the debian directory[3], but ci.d.o, to my surprise,
is running autopkgtest[4] on this package.
As far as I know, tests are defined in debian/tests/control when the
tester is autopkgtest. No test will be run if the tests control file
doesn't exist. That being said, things happend on the ujson package
looks very confusin ... Does anyone know what happend?
One of my wild guesses is that, the ci.d.o infractructure conducts
some basic sanity tests on python packages in which the tests control file
doesn't exist. See the quote from ci.d.o log:
> set -e ; for py in $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c "import ujson; print(ujson)" ; done
Where did that test come from? Thanks.
[1] https://salsa.debian.org/python-team/modules/ujson
[2] http://tracker.debian.org/ujson
[3] https://salsa.debian.org/python-team/modules/ujson/tree/master/debian
[4] https://ci.debian.net/data/autopkgtest/unstable/amd64/u/ujson/365717/log.gz
Reply to: