Bug#1029310: [Help] Re: Bug#1029310: src:r-cran-bayesplot: fails to migrate to testing for too long: autopkgtest regression

2023-01-23 Thread Andreas Tille
Hi Nilesh,

Am Mon, Jan 23, 2023 at 03:49:29PM +0530 schrieb Nilesh Patra:
> >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.
> 
> I did find an issue[3] which states ggplot2 breaks bayesplot 1.9.0 and spews 
> the exact same errors we observe in debci.
> There's also an upstream issue with bayesplot installation (similar stuff 
> again) where it works for some people but not for others, see[4].
> But then I'm not sure as to why it works for me, you and salsa CI. For now 
> I'll have to dismiss it by calling it black magic.
> 
> Your approach sounds fair. Maybe you should do what you wrote (disable tests, 
> let it migrate, enable tests again)

I did so just to learn that there are new errors now[5].  I admit I've
lost my nerves and uploaded by really forcing acceptance of all errors[6].
I'll revert this after testing migration as well as the patch I tried
before.

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
> [3]: 
> https://github.com/tidyverse/ggplot2/blob/main/revdep/problems.md#bayesplot
> [4]: 
> https://github.com/stan-dev/bayesplot/issues/297

[5] 
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-bayesplot/30633104/log.gz
 
[6] 
https://salsa.debian.org/r-pkg-team/r-cran-bayesplot/-/blob/master/debian/tests/run-unit-test#L15

-- 
http://fam-tille.de



Bug#1029310: [Help] Re: Bug#1029310: src:r-cran-bayesplot: fails to migrate to testing for too long: autopkgtest regression

2023-01-23 Thread Nilesh Patra



On 23 January 2023 3:06:58 pm IST, Andreas Tille  wrote:
>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: 
> [...]
>
>to me those diffs are locking not really spectacular regarding to
>the actual issue.

Right.

>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.

I did find an issue[3] which states ggplot2 breaks bayesplot 1.9.0 and spews 
the exact same errors we observe in debci.
There's also an upstream issue with bayesplot installation (similar stuff 
again) where it works for some people but not for others, see[4].
But then I'm not sure as to why it works for me, you and salsa CI. For now I'll 
have to dismiss it by calling it black magic.

Your approach sounds fair. Maybe you should do what you wrote (disable tests, 
let it migrate, enable tests again)

>[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
[3]: https://github.com/tidyverse/ggplot2/blob/main/revdep/problems.md#bayesplot
[4]: 
https://github.com/stan-dev/bayesplot/issues/297
--
Best,
Nilesh



Bug#1029310: [Help] Re: Bug#1029310: src:r-cran-bayesplot: fails to migrate to testing for too long: autopkgtest regression

2023-01-23 Thread Andreas Tille
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   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



Bug#1029310: [Help] Re: Bug#1029310: src:r-cran-bayesplot: fails to migrate to testing for too long: autopkgtest regression

2023-01-21 Thread 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.

Thanks
Nilesh



Bug#1029310: [Help] Re: Bug#1029310: src:r-cran-bayesplot: fails to migrate to testing for too long: autopkgtest regression

2023-01-21 Thread Andreas Tille
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?
 
> I'm suspecting there is some dependency problem here.

I also suspected this but the only hint about issues given by the log was
ggplot2 which was not changed a long time.

Kind regards
   Andreas.
 
> > [1] 
> > https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-bayesplot/30534574/log.gz
> > [2] https://salsa.debian.org/r-pkg-team/r-cran-bayesplot/-/jobs/3779597
> 
> Thanks
> Nilesh
> 
> ___
> R-pkg-team mailing list
> r-pkg-t...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/r-pkg-team
> 

-- 
http://fam-tille.de



Bug#1029310: [Help] Re: Bug#1029310: src:r-cran-bayesplot: fails to migrate to testing for too long: autopkgtest regression

2023-01-21 Thread 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. 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?

I'm suspecting there is some dependency problem here.


[1] 
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-bayesplot/30534574/log.gz
[2] https://salsa.debian.org/r-pkg-team/r-cran-bayesplot/-/jobs/3779597


Thanks
Nilesh



Bug#1029310: [Help] Re: Bug#1029310: src:r-cran-bayesplot: fails to migrate to testing for too long: autopkgtest regression

2023-01-21 Thread Andreas Tille
Control: tags -1 help
Control: reopen -1
 (reopening to make sure we will not overlook this bug)

Hi,

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.

Kind regards
Andreas.


[1] 
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-bayesplot/30534574/log.gz
[2] https://salsa.debian.org/r-pkg-team/r-cran-bayesplot/-/jobs/3779597

-- 
http://fam-tille.de