Am Sat, Jan 21, 2023 at 10:17:06PM +0530 schrieb Nilesh Patra: > On 1/21/23 21:59, Andreas Tille wrote: > > Am Sat, Jan 21, 2023 at 09:46:07PM +0530 schrieb Nilesh Patra: > > > On 1/21/23 16:56, Andreas Tille wrote: > > > > as per DebCI there are 15 autopkgtest failures which seem to be > > > > connected to ggplot2 API somehow.[1] Interestingly Salsa CI[2] does not > > > > show this autopkgtest error neither can I reproduce the problem on my > > > > local > > > > pbuilder. > > > > > > > > Has anyone some idea what might be wrong? If not I might ask bug > > > > reporter > > > > for more info. > > > > > > I can't repro it either. > > > > Relieving to know that I did not missed any basic thing here. ;-) > > > > > But the log you point to is a fresh failure (today). > > > Did not dig deeper, but did you take a look at the `diff` between log > > > that passes and the one > > > which does not? > > > > Not yet. Where can I find those old logs? > > You can take a diff betweek ci log you pointed to and the log on salsa > CI/local system. > The debci runs with package versions in testing, so there might be a bump in > some dependency.
I did a diff between the r-cran-* packages in the failing log and the successful log: --- debci (with dependencies from testing which fails https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-bayesplot/30584842/log.gz +++ salsa (with dependencies from unstable which works) @@ -2,8 +2,8 @@ @@ -153,12 +153,13 @@ -r-base-core_4.2.2.20221110-1+b1_amd64.deb +r-base-core_4.2.2.20221110-1_amd64.deb -r-cran-bayesplot_1.9.0-1_all.deb +r-cran-bayesplot.deb -r-cran-cli_3.6.0-1_amd64.deb +r-cran-cli_3.5.0-1_amd64.deb -r-cran-ggplot2_3.4.0+dfsg-2_all.deb +r-cran-ggplot2_3.4.0+dfsg-1_all.deb -r-cran-htmlwidgets_1.6.1+dfsg-1_all.deb -r-cran-httpuv_1.6.8+dfsg-1_amd64.deb +r-cran-htmlwidgets_1.6.0+dfsg-1_all.deb +r-cran-httpuv_1.6.7+dfsg-1_amd64.deb -r-cran-purrr_0.3.5-1_amd64.deb +r-cran-purrr_1.0.0-1_amd64.deb -r-cran-rcppparallel_5.1.6+dfsg-1_amd64.deb +r-cran-rcppparallel_5.1.5+dfsg-3_amd64.deb -r-cran-statmod_1.5.0-1_amd64.deb -r-cran-stringi_1.7.12-1_amd64.deb -r-cran-stringr_1.4.1-1_all.deb +r-cran-statmod_1.4.37-1_amd64.deb +r-cran-stringi_1.7.8-1+b1_amd64.deb +r-cran-stringr_1.5.0-1_all.deb -r-cran-xts_0.12.1-1_amd64.deb +r-cran-xts_0.12.2-1_amd64.deb to me those diffs are locking not really spectacular regarding to the actual issue. I also checked the debci history[1] where the first failure of this kind is 1.9.0-1 2022-11-11 23:59:45 UTC r-cran-ggplot2/3.4.0+dfsg-1 diffoscop... src:r-cran-ggplot2 from unstable src:diffoscope from unstable src:r-base from unstable src:r-cran-vctrs from unstable where I can find inside the test log[2] This might correlate to r-cran-ggplot2 (3.4.0+dfsg-1) unstable; urgency=medium * New upstream version ... -- Andreas Tille <[email protected]> Fri, 11 Nov 2022 08:24:21 +0100 I admit I'm running out of ideas but for the moment my last resort is to skip the 8 affected test, let the packages migrate to testing and revert skipping the tests afterwards. Kind regards Andreas. [1] https://ci.debian.net/packages/r/r-cran-bayesplot/testing/amd64/ [2] https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-bayesplot/28139180/log.gz -- http://fam-tille.de
