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

2024-03-18 Thread 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

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

2024-03-17 Thread Ben Bolker
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

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

2024-03-17 Thread Ivan Krylov via R-package-devel
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

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

2024-03-17 Thread Ben Bolker
Hi folks, We're in the final stages of preparing a revised version of the glmmTMB package for CRAN and are stuck troubleshooting checks on win-builder/r-devel. Testing is working everywhere *except* win-builder/r-devel. Win-builder is OK with r-oldrel and r-devel; the same package is