autodep8 needs support for pybuild-autopkgtest
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Auto Package Testing |
Fix Released
|
High
|
Brian Murray |
Bug Description
In autodep8 version 0.28, the following changelog entry exists:
* Add support for pybuild-
`Testsuite: autopkgtest-
usage details.
Packages in Debian have started to transition over, an example being python-hypothesis. In Debian Unstable, the full testsuite is ran as expected:
I: pybuild base:240: cd /tmp/autopkgtes
And indeed, this is what upstream expects for automated testing. However, in Ubuntu this is the entire "test":
autopkgtest [01:13:55]: test autodep8-python3: set -e ; for py in $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c "import hypothesis; print(hypothesis)" ; done
Importing the Python module and printing out an object representation can hardly be considered a test suite. While there is no debian/tests directory, the Debian Maintainer likely expects tests to be ran, given that "Testsuite: autopkgtest-
Here is a rough package count:
$ grep-dctrl --show-field Package -F Testsuite "autopkgtest-
88
While I do not have direct SSH access to the autopkgtest cloud, from reading the code it seems clear to me that autodep8 is built from source, from this Git repository: https:/
References:
- https:/
- https:/
- https:/
The aforementioned autodep8 repository needs an update, and someone with SSH access should run the following (per the admin reference guide):
$ juju run-action <unit> update-sources
(where <unit> is the cloud/lxd worker shown in juju status)
Related branches
- Brian Murray: Approve
-
Diff: 623 lines (+242/-44)26 files modified.launchpad.yaml (+1/-1)
README.md (+12/-2)
debian/changelog (+61/-0)
debian/control (+3/-4)
debian/tests/control (+1/-0)
debian/tests/test-package-type (+22/-17)
examples.in (+4/-3)
examples.md (+8/-5)
support/autodep8lib.sh (+6/-1)
support/dkms/detect (+1/-1)
support/dkms/generate (+6/-2)
support/elpa/generate (+4/-0)
support/go/generate (+6/-0)
support/nodejs/generate (+7/-0)
support/octave/generate (+7/-3)
support/perl/generate (+10/-0)
support/pybuild/detect (+3/-0)
support/pybuild/generate (+14/-0)
support/python/generate (+11/-2)
support/r/generate (+4/-0)
support/ruby/generate (+4/-0)
test/autodep8lib_test.sh (+1/-1)
test/common_config_test.sh (+7/-0)
test/dkms_test.sh (+5/-0)
test/octave_test.sh (+3/-2)
test/pybuild_test.sh (+31/-0)
description: | updated |
When you say "someone with SSH access should run the following (per the admin reference guide)" what admin reference guide are you referring to? I think this is the first time I've heard of "juju run-action".