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&arch=all&ver=4.5.2%2Bdfsg.1-2&stamp=1572147897&raw=0 shows the documentation can now be found in /usr/share/doc/python-coverage-doc/html/index.html >> In tabular form: >> pass fail >> python-coverage from testing 4.5.2+dfsg.1-2 >> all others from testing from 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
