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

@github-actions crossbow submit -g r

Revision: bf18353

Submitted crossbow builds: ursacomputing/crossbow @ actions-a14f05c971

Task	Status
r-binary-packages
r-recheck-most
test-r-arrow-backwards-compatibility
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-sanitizers
test-r-linux-valgrind
test-r-m1-san
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

After this merges, I'll take a look at rebasing #41998 as it removes the one thing we weren't sure about there

After this merges, I'll take a look at rebasing #41998 as it removes the one thing we weren't sure about there

😦 We've blocked things for ~1 year due to this 😦 That's unfortunate.

But, yes, please! 🙏 I think technically that could merge now since we bumped to 19.0.1 a little while ago already, but waiting until this PR merges is also totally fine.

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

There were no benchmark performance regressions. 🎉

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