Le 14/09/2017 à 08:43, Rafael Laboissière a écrit :
And here is the recipe for running the tests (from the package
source in the current Git version):
autopkgtest -B . -- null
Here is what I get with octave-stk:
autopkgtest [12:32:11]: version 4.4 autopkgtest [12:32:11]: host
EliteBookZZ; command line: /usr/bin/autopkgtest -B . -- null
autopkgtest [12:32:11]: testbed dpkg architecture: amd64 autopkgtest
[12:32:11]: testbed running kernel: Linux 4.9.0-3-amd64 #1 SMP Debian
4.9.30-2+deb9u3 (2017-08-06) autopkgtest [12:32:11]:
@@@@@@@@@@@@@@@@@@@@ unbuilt-tree . dpkg-source: info: mise en place
de 0001-Remove-stk_config_testprivatemex.patch dpkg-source: info:
mise en place de 0002-Remove-the-MOLE.patch autopkgtest [12:32:12]:
testing package octave-stk version 2.4.2-1 autopkgtest [12:32:12]:
build not needed * SKIP no tests in this package autopkgtest
[12:32:12]: @@@@@@@@@@@@@@@@@@@@ summary * SKIP no
tests in this package
There (many) unit tests in octave-stk but they are not detected.
I suspect that the problem comes from the multi-directory structure
of the package. If it is so, other packages will have the same issue
(geometry, for instance).
To run the unit tests in STK, you can just type stk_runtests (or use
directly __run_test_suite__ as is done in stk_runtests).
Let me know what I can do to help you fix this.