Closed zeroshade closed 3 days ago
:warning: GitHub issue #44734 has been automatically assigned in GitHub to PR creator.
@github-actions crossbow submit -g cpp
Revision: 64bc0002d2ce9af369418caca460f90a17db6195
Submitted crossbow builds: ursacomputing/crossbow @ actions-6635482d34
@github-actions crossbow submit -g cpp
Revision: 26d5813af3b4edb4d2e51a351c4492a81241e43f
Submitted crossbow builds: ursacomputing/crossbow @ actions-31c2edbae5
@github-actions crossbow submit -g cpp
Revision: 32cb80b3e660a4355ae54490419f2524ab0270e0
Submitted crossbow builds: ursacomputing/crossbow @ actions-fe93653fee
After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit 4dc0492161f5653ce759d1f5796ce69e1d822f44.
There were no benchmark performance regressions. 🎉
The full Conbench report has more details. It also includes information about 3 possible false positives for unstable benchmarks that are known to sometimes produce them.
Rationale for this change
The Async C Device Stream Interface unit tests requiring threading to be enabled, but a couple of our CI runs go with ARROW_ENABLE_THREADING disabled.
What changes are included in this PR?
The Async C Device Stream interface tests are guarded with
#ifdef ARROW_ENABLE_THREADING
to prevent CI timeouts.