Bug#944076: python-coverage: autopkgtest regression: Can't load /usr/share/doc/python-coverage/html/index.html
Hi Ben, On 03-11-2019 22:17, Ben Finney wrote: > On 03-Nov-2019, Paul Gevers wrote: > >> With a recent upload of python-coverage the autopkgtest of >> python-coverage fails in testing when that autopkgtest is run with the >> binary packages of python-coverage from unstable. It passes when run >> with only packages from testing. > > Thank you for investigating this difference between environments. Sure. That is how our migration software works nowadays. >> I copied some of the output at the bottom of this report. > > I see that the build log does not show any output at all for > attempting to build the documentation; for some reason that step is > being silently omitted. I will investigate why. Are you talking about the autopkgtest here? You don't declare a build-needed restriction so that's expected. If your talking about buildd logs, I'll shut up. I noticed in your changelog that you bumped debhelper compat level. Please be aware the the directory where the documentation goes can change that way. https://buildd.debian.org/status/fetch.php?pkg=python-coverage=all=4.5.2%2Bdfsg.1-2=1572147897=0 shows the documentation can now be found in /usr/share/doc/python-coverage-doc/html/index.html >> In tabular form: >>passfail >> python-coveragefrom testing4.5.2+dfsg.1-2 >> all others from testingfrom testing > > Is there anywhere I can see the output from a successful build of this > package release? Huh, no. It always fails. > Or, do you mean that the success is for a *different* (previous?) > release of ‘python-coverage’? Yes. The current version in testing passes. The current version in unstable fails if that is included in testing. > Also, what does “all others” represent here; what packages? https://ci.debian.net/data/packages/testing/amd64/p/python-coverage/3331284.log Or, check the *-packages files in https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-coverage/3331284/artifacts.tar.gz for a clean list per test. Paul signature.asc Description: OpenPGP digital signature
Bug#944076: python-coverage: autopkgtest regression: Can't load /usr/share/doc/python-coverage/html/index.html
On 03-Nov-2019, Paul Gevers wrote: > With a recent upload of python-coverage the autopkgtest of > python-coverage fails in testing when that autopkgtest is run with the > binary packages of python-coverage from unstable. It passes when run > with only packages from testing. Thank you for investigating this difference between environments. > I copied some of the output at the bottom of this report. I see that the build log does not show any output at all for attempting to build the documentation; for some reason that step is being silently omitted. I will investigate why. > In tabular form: >passfail > python-coveragefrom testing4.5.2+dfsg.1-2 > all others from testingfrom testing Is there anywhere I can see the output from a successful build of this package release? Or, do you mean that the success is for a *different* (previous?) release of ‘python-coverage’? Also, what does “all others” represent here; what packages? -- \“I don't accept the currently fashionable assertion that any | `\ view is automatically as worthy of respect as any equal and | _o__) opposite view.” —Douglas Adams | Ben Finney signature.asc Description: PGP signature
Bug#944076: python-coverage: autopkgtest regression: Can't load /usr/share/doc/python-coverage/html/index.html
Source: python-coverage Version: 4.5.2+dfsg.1-2 X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: regression Dear maintainers, With a recent upload of python-coverage the autopkgtest of python-coverage fails in testing when that autopkgtest is run with the binary packages of python-coverage from unstable. It passes when run with only packages from testing. In tabular form: passfail python-coveragefrom testing4.5.2+dfsg.1-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=python-coverage https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-coverage/3323210/log.gz autopkgtest [05:10:13]: test command1: w3m -dump /usr/share/doc/python-coverage/html/index.html > /dev/null autopkgtest [05:10:13]: test command1: [--- w3m: Can't load /usr/share/doc/python-coverage/html/index.html. autopkgtest [05:10:13]: test command1: ---] autopkgtest [05:10:50]: test command2: file --brief /usr/share/doc/python-coverage/html/index.html| grep -q 'HTML document' autopkgtest [05:10:50]: test command2: [--- autopkgtest [05:10:51]: test command2: ---] autopkgtest [05:10:51]: test command2: - - - - - - - - - - results - - - - - - - - - - command2 FAIL non-zero exit status 1 signature.asc Description: OpenPGP digital signature
