Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
kou opened this issue Dec 23, 2022 · 6 comments · Fixed by #25359
Closed

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

kou opened this issue Dec 23, 2022 · 6 comments · Fixed by #25359

Comments

@kou
Copy link
Member

kou commented Dec 23, 2022

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
Copy link
Member

assignUser commented Dec 23, 2022

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

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

@kou
Copy link
Member Author

kou commented Dec 23, 2022

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
Copy link
Member

purrr will release a fix to cran in early january

@kou
Copy link
Member Author

kou commented Dec 27, 2022

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

@assignUser
Copy link
Member

assignUser commented Jan 6, 2023

this now also causes an ERROR on CRAN @nealrichardson

@nealrichardson
Copy link
Member

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.

kou pushed a commit that referenced this issue Jan 10, 2023
…25359)

# Which issue does this PR close?

purrr 1.0.1 is released on cran

Closes #15080 
* Closes: #15080

Authored-by: Jacob Wujciak-Jens <jacob@wujciak.de>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
@kou kou added this to the 11.0.0 milestone Jan 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment