@github-actions crossbow submit -g r

⚠️ GitHub issue #44127 has been automatically assigned in GitHub to PR creator.

Any idea what's going on with the binary builds @assignUser ?

I'm seeing Error: Unable to find any artifacts for the associated workflow and then it looks like we're getting release versions after that (which we rightfully catch!) I've not seen that before

Ah, we're mixing download-artifact@v4 and upload-artifact@v3.

@github-actions crossbow submit -g r

Revision: 6ec3ced

Submitted crossbow builds: ursacomputing/crossbow @ actions-ed4573519f

Task	Status
r-binary-packages
test-r-arrow-backwards-compatibility
test-r-clang-sanitizer
test-r-depsource-bundled
test-r-depsource-system
test-r-dev-duckdb
test-r-devdocs
test-r-extra-packages
test-r-gcc-11
test-r-gcc-12
test-r-install-local
test-r-install-local-minsizerel
test-r-linux-as-cran
test-r-linux-rchk
test-r-linux-valgrind
test-r-macos-as-cran
test-r-minimal-build
test-r-offline-maximal
test-r-offline-minimal
test-r-rhub-debian-gcc-devel-lto-latest
test-r-rhub-debian-gcc-release-custom-ccache
test-r-rhub-ubuntu-release-latest
test-r-rocker-r-ver-latest
test-r-rstudio-r-base-4.1-opensuse155
test-r-rstudio-r-base-4.2-focal
test-r-ubuntu-22.04
test-r-versions
test-ubuntu-r-sanitizer

After merging your PR, Conbench analyzed the 4 benchmarking runs that have been run so far on merge-commit c3a0bd2.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 4 possible false positives for unstable benchmarks that are known to sometimes produce them.