[Pkg-octave-devel] Autopkgtest for the OF packages

[Julien Bect]

Le 14/09/2017 à 08:43, Rafael Laboissière a écrit :
> * Sébastien Villemot <sebastien at debian.org> [2017-09-13 13:44]:
>
>> On Wed, Sep 13, 2017 at 11:44:18AM +0200, Rafael Laboissière wrote:
>>> Version 1.5.1 of octave-pkg-dev has got out the NEW queue and 
>>> version 0.10
>>> of autodep8, with Octave support added by yours truly, is now in 
>>> unstable.
>>> Everything is ready now to have the Debian Octave-Forge packages being
>>> autotested by the Debian Continuous Integration infrastructure [*].
>>>
>>> In order for that to happen, the field 
>>> "Testsuite: autopkgtest-pkg-octave" must appear in the source stanza 
>>> of debian/control.  I just did it with a mass-commit to the Git 
>>> repositories.  I apologize in advance if something got screwed up 
>>> with by my semi-automatic procedure.
>>
>> Great news, thanks a lot!
>
> And here is the recipe for running the tests (from the package source 
> in the current Git version):
>
>    autopkgtest -B . -- null
>
> Rafael

Hi Rafael,

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.

@++
Julien