-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
GH-41127: [CI] Use GitHub Actions instead of Azure Pipelines for docker-tests #41153
Conversation
…r docker-tests We don't want to maintain multiple CI platforms to reduce maintenance cost.
|
@github-actions crossbow submit test-conda-cpp-valgrind test-debian-12-python-3-amd64 test-ubuntu-20.04-python-3 test-fedora-39-python-3 test-r-linux-valgrind test-ubuntu-r-sanitizer test-fedora-r-clang-sanitizer test-debian-12-go-* |
Revision: bbabac5 Submitted crossbow builds: ursacomputing/crossbow @ actions-68d49ae06b |
Oh this is great! Thank you kou! |
I think that the test-conda-cpp-valgrind failure is unrelated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Thanks @kou
We don't need #41004 for 16.0.0! |
After merging your PR, Conbench analyzed the 4 benchmarking runs that have been run so far on merge-commit 86395b0. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 14 possible false positives for unstable benchmarks that are known to sometimes produce them. |
…r docker-tests (apache#41153) ### Rationale for this change We don't want to maintain multiple CI platforms to reduce maintenance cost. ### What changes are included in this PR? Use GitHub Actions for docker-tests. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * GitHub Issue: apache#41127 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
…r docker-tests (apache#41153) ### Rationale for this change We don't want to maintain multiple CI platforms to reduce maintenance cost. ### What changes are included in this PR? Use GitHub Actions for docker-tests. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * GitHub Issue: apache#41127 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
…r docker-tests (apache#41153) ### Rationale for this change We don't want to maintain multiple CI platforms to reduce maintenance cost. ### What changes are included in this PR? Use GitHub Actions for docker-tests. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * GitHub Issue: apache#41127 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
…r docker-tests (apache#41153) ### Rationale for this change We don't want to maintain multiple CI platforms to reduce maintenance cost. ### What changes are included in this PR? Use GitHub Actions for docker-tests. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * GitHub Issue: apache#41127 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
…r docker-tests (apache#41153) ### Rationale for this change We don't want to maintain multiple CI platforms to reduce maintenance cost. ### What changes are included in this PR? Use GitHub Actions for docker-tests. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * GitHub Issue: apache#41127 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
…r docker-tests (apache#41153) ### Rationale for this change We don't want to maintain multiple CI platforms to reduce maintenance cost. ### What changes are included in this PR? Use GitHub Actions for docker-tests. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * GitHub Issue: apache#41127 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
Rationale for this change
We don't want to maintain multiple CI platforms to reduce maintenance cost.
What changes are included in this PR?
Use GitHub Actions for docker-tests.
Are these changes tested?
Yes.
Are there any user-facing changes?
No.