[R-pkg-devel] help diagnosing win-builder failures

[Uwe Ligges]

On 18.03.2024 02:07, Ben Bolker wrote:
>    I think I may actually have figured this out.
> 
>    The Matrix package is being updated to version 1.7.0 soon, with 
> expected ABI breakage.  This version is **already installed on 
> win-builder/r-devel**, so the Matrix/TMB/glmmTMB binary stack fails 
> (digging into the logs a bit deeper showed that the *first* instance of 
> a call to glmmTMB in any example/test/prior was failing ...)
> 
>    I think the only way to solve this is to bump/re-install the version 
> of TMB that lives on win-builder.
> 
>    For the record, this will probably bite any package that depends on 
> Matrix ABI ...

This is only in the on demand check queue (not the daily CRAN repository 
checks nor the incoming checks) due to a recently checked Matrix in that 
queue (that would be auto-removed soon, but I'll trigger this manually now).

Best,
Uwe Ligges



> On 2024-03-17 4:42 p.m., Ivan Krylov wrote:
>> Hi,
>>
>> This may need the help of Uwe Ligges to diagnose. I suspect this may be
>> related to the Windows machine having too much memory committed (as Uwe
>> has been able to pinpoint recently [*] about a package that failed to
>> compile some heavily templated C++), but there is not enough information
>> to give a conclusive diagnosis.
>>
>> On Sun, 17 Mar 2024 14:01:33 -0400
>> Ben Bolker <bbolker using gmail.com> wrote:
>>
>>> 2. an ERROR running tests, where the output ends with a cryptic
>>>
>>>     Anova: ..
>>>
>>> (please try to refrain from snarky comments about not using testthat
>>> ...)
>>
>> Pardon my ignorance, but is it an option to upload a version of the
>> package that uses test_check(pkg, reporter=LocationReporter()) instead
>> of the summary reporter?
> 
>    I don't know, could be worth a try.
> 
> 
>>
> 
> 
>    cheers
>     Ben Bolker
> 
> ______________________________________________
> R-package-devel using r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel