Source: autopkgtest Version: 5.2 Severity: normal User: debian...@lists.debian.org Usertags: issue
In the case of migration testing, the following issue may occur. autopkgtest inspects the test of package A from testing, as that is what it wants to run. Then, it requests apt to install package B (the package under investigation for migration) from unstable. Due to dependency issues (not clear to me where this goes wrong yet in this case, but there is an autopkgtest fallback mode ongoing), package A may actually be installed from unstable and there is a mismatch between the test version and the tested version of package A, causing undesired failure. A current example is fig2dev which is run for texlive-base (log attached, taken from https://ci.debian.net/data/autopkgtest/testing/amd64/f/fig2dev/180600/log.gz). 1:3.2.6a-6 2018-04-18 12:51:38 UTC migration-reference/0 0h 1m 2s pass debci log test log artifacts 1:3.2.6a-6 2018-04-18 12:51:36 UTC texlive-base/2018.20180416-1 0h 1m 3s fail debci log test log artifacts 1:3.2.7-2 2018-04-15 10:13:43 UTC fig2dev/1:3.2.7-2 0h 1m 16s pass debci log test log artifacts I am filling this bug to store the information. I don't know yet what autopkgtest should actually do in this case. Maybe the solution lies even with britney, that could become smarter in triggering. If it already knows there is a dependency issue, it could trigger the set, such that the test suite is already taken from unstable to begin with. Paul
fig2dev_testing_with_texlive-base.log.gz
Description: application/gzip
signature.asc
Description: OpenPGP digital signature
