-
Notifications
You must be signed in to change notification settings - Fork 4k
WIP: [R] Verify CRAN release-10.0.1-rc0 #14772
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
Conversation
|
Thanks for opening a pull request! If this is not a minor PR. Could you open an issue for this pull request on JIRA? https://issues.apache.org/jira/browse/ARROW Opening JIRAs ahead of time contributes to the Openness of the Apache Arrow project. Then could you also rename pull request title in the following format? or See also: |
|
@github-actions crossbow submit -g r* |
|
|
@github-actions crossbow submit -g r |
|
Revision: 0fbe35f Submitted crossbow builds: ursacomputing/crossbow @ actions-bcb1b6db16 |
|
@github-actions crossbow submit test-r-linux-valgrind |
|
failing jobs:
|
|
Revision: 0fbe35f Submitted crossbow builds: ursacomputing/crossbow @ actions-c4e0abbfb4
|
|
The valgrind job will almost certainly time out again (or fail if it does not); however, it did so prior to the 10.0.0 release as well (I've made some progress and it will hopefully be fixed by 11.0.0). The homebrew/autobrew failures are expected: they did so prior to the 10.0.0 release as well (I've made some progress and it will hopefully be fixed by 11.0.0). I don't have a good handle on the devdocs failures; however given that our other ubuntu jobs are passing I wonder if it's cache-related or related to the divergence between master and the RC branch? |
No description provided.