Skip to content

Conversation

@thisisnic
Copy link
Member

No description provided.

@github-actions
Copy link

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?

ARROW-${JIRA_ID}: [${COMPONENT}] ${SUMMARY}

or

MINOR: [${COMPONENT}] ${SUMMARY}

See also:

@thisisnic thisisnic changed the title Arbitrary whitespace for PR [Do not merge] Run R tests on release candidate Nov 29, 2022
@thisisnic
Copy link
Member Author

@github-actions crossbow submit -g r*

@github-actions
Copy link

Invalid group(s) {'r*'}. Must be one of {'example', 'python', 'verify-rc-source', 'nightly-release', 'conda', 'conan', 'verify-rc-jars', 'ruby', 'verify-rc-source-macos', 'packaging', 'wheel', 'c-glib', 'r', 'homebrew', 'nightly-tests', 'test', 'linux-arm64', 'example-cpp', 'vcpkg', 'verify-rc-binaries', 'linux-amd64', 'integration', 'verify-rc-source-linux', 'fuzz', 'linux', 'nightly', 'nightly-packaging', 'verify-rc', 'cpp', 'example-python', 'verify-rc-wheels'}
The Archery job run can be found at: https://github.com/apache/arrow/actions/runs/3575322370

@thisisnic thisisnic changed the title [Do not merge] Run R tests on release candidate WIP: [R] Verify CRAN release-10.0.1-rc0 Nov 29, 2022
@thisisnic
Copy link
Member Author

@github-actions crossbow submit -g r

@github-actions
Copy link

Revision: 0fbe35f

Submitted crossbow builds: ursacomputing/crossbow @ actions-bcb1b6db16

Task Status
conda-linux-gcc-py37-cpu-r40 Azure
conda-linux-gcc-py37-cpu-r41 Azure
conda-osx-clang-py37-r40 Azure
conda-osx-clang-py37-r41 Azure
conda-win-vs2019-py37-r40 Azure
conda-win-vs2019-py37-r41 Azure
homebrew-r-autobrew Github Actions
homebrew-r-brew Github Actions
r-binary-packages Github Actions
test-fedora-r-clang-sanitizer Azure
test-r-arrow-backwards-compatibility Github Actions
test-r-depsource-bundled Azure
test-r-depsource-system Github Actions
test-r-dev-duckdb Github Actions
test-r-devdocs Github Actions
test-r-gcc-11 Github Actions
test-r-gcc-12 Github Actions
test-r-install-local Github Actions
test-r-install-local-minsizerel Github Actions
test-r-linux-as-cran Github Actions
test-r-linux-rchk Github Actions
test-r-linux-valgrind Azure
test-r-minimal-build Azure
test-r-offline-maximal Github Actions
test-r-offline-minimal Azure
test-r-rhub-debian-gcc-devel-lto-latest Azure
test-r-rhub-debian-gcc-release-custom-ccache Azure
test-r-rhub-ubuntu-gcc-release-latest Azure
test-r-rocker-r-base-latest Azure
test-r-rstudio-r-base-4.1-opensuse153 Azure
test-r-rstudio-r-base-4.2-centos7-devtoolset-8 Azure
test-r-rstudio-r-base-4.2-focal Azure
test-r-ubuntu-22.04 Github Actions
test-r-versions Github Actions
test-ubuntu-18.04-r-sanitizer Azure

@thisisnic
Copy link
Member Author

@github-actions crossbow submit test-r-linux-valgrind

@thisisnic
Copy link
Member Author

thisisnic commented Nov 30, 2022

failing jobs:

@github-actions
Copy link

Revision: 0fbe35f

Submitted crossbow builds: ursacomputing/crossbow @ actions-c4e0abbfb4

Task Status
test-r-linux-valgrind Azure

@paleolimbot
Copy link
Member

paleolimbot commented Nov 30, 2022

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?

@thisisnic thisisnic closed this Dec 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants