Bug#1010074: RFS: show-in-file-manager/1.1.4-1 [RFP] -- Open the system file manager and optionally select files in it
On 2022-04-24 21:57:09, Tino Mettler wrote:
> Am 24.04.2022 um 21:41 schrieb Antoine Beaupré <anarcat@debian.org>:
>>
>> Hi!
>>
>> I tested the package and it generally looks good, but tests fail in
>> autopkgtest:
>>
>> autopkgtest [15:28:00]: test autodep8-python3: set -e ; for py in $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c "import showinfilemanager; print(showinfilemanager)" ; done
>> autopkgtest [15:28:00]: test autodep8-python3: [-----------------------
>> Testing with python3.9:
>> Traceback (most recent call last):
>> File "<string>", line 1, in <module>
>> ModuleNotFoundError: No module named 'showinfilemanager'
>> autopkgtest [15:28:01]: test autodep8-python3: -----------------------]
>> autopkgtest [15:28:02]: test autodep8-python3: - - - - - - - - - - results - - - - - - - - - -
>> autodep8-python3 FAIL non-zero exit status 1
>> autopkgtest [15:28:03]: @@@@@@@@@@@@@@@@@@@@ summary
>> autodep8-python3 FAIL non-zero exit status 1
>> qemu-system-x86_64: terminating on signal 15 from pid 136604 (/usr/bin/python3)
>>
>>
>> I'm doing this in a new qemu-based setup so it's possible this is due to
>> my setup, can you reproduce?
>
> Hi,
>
> I've never worked with autopkgtest. My last upload was a few years ago when the autotestpkg stuff was quite new. What do I need to do in order to reproduce this? In my pbuilder log, I just see this:
>
> dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:239: cd /build/show-in-file-manager-1.1.4/.pybuild/cpython3_3.9/build; python3.9 -m unittest discover -v
>
> ----------------------------------------------------------------------
> Ran 0 tests in 0.000s
>
> OK
> I: pybuild base:239: cd /build/show-in-file-manager-1.1.4/.pybuild/cpython3_3.10/build; python3.10 -m unittest discover -v
>
> ----------------------------------------------------------------------
> Ran 0 tests in 0.000s
>
> OK
Yeah, so that is the test suite running (or failing to be detected, to
be more accurate) at *build* time. Autopkgtest runs the test suite
*after* the package is build, with the built package.
You have actually configured it in the package, so it would be better if
it actually works. :) Try just running `autopkgtest` in the source
directory..
https://wiki.debian.org/ContinuousIntegration/autopkgtest
A.
--
How inappropriate to call this planet 'Earth' when it is quite clearly
'Ocean'.
- Arthur C. Clarke
Reply to: