[CI][R] Binary package job for R 4.1 on Windows is failed with purrr 1.0.0

[kou]

Describe the bug, including details regarding any error messages, version, and platform.

With purrr 0.3.5 (success): https://github.com/ursacomputing/crossbow/actions/runs/3756216656/jobs/6382536442

With purrr 1.0.0 (failed): https://github.com/ursacomputing/crossbow/actions/runs/3756216656/jobs/6406276507

** testing if installed package can be loaded from temporary location
*** arch - i386
Error: Error: package or namespace load failed for 'arrow' in library.dynam(lib, package, package.lib):
*** arch - x64
 DLL 'purrr' not found: maybe not installed for this architecture?
Error: Error: loading failed

Note that the above two jobs are the same revision. The former was ran at 2022-12-22. The latter was re-ran at 2022-12-24.

https://cran.r-project.org/package=purrr says purrr 1.0.0 was published at 2022-12-20:

Published: 2022-12-20

Note that R 4.2 on Windows job doesn't have this problem.

Component(s)

Continuous Integration, Packaging, R

[assignUser]

Purrr already has a patch merged: tidyverse/purrr#1017

We could switch to purr Dev version until it is on cran?

[kou]

Purrr already has a patch merged: tidyverse/purrr#1017

Thanks for the information!

We could switch to purr Dev version until it is on cran?

It's an option.

I skipped R 4.1 on Windows job in #15075 .

[assignUser]

purrr will release a fix to cran in early january

[kou]

Thanks for the information!
I've disabled the job in #15075. So we can revert it after purrr is released.

[assignUser]

this now also causes an ERROR on CRAN @nealrichardson

[nealrichardson]

this now also causes an ERROR on CRAN @nealrichardson

👍 will keep an eye on it. CRAN hasn't bugged me about it; I'm guessing they know what's up.