-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[CI][Archery] Some Azure jobs fail on pip install -e arrow/dev/archery[docker] #41127
Comments
Hmm. It seems that
Could you try this on diff --git a/dev/tasks/docker-tests/azure.linux.yml b/dev/tasks/docker-tests/azure.linux.yml
index b66bfbdfe9..a2c49d9f29 100644
--- a/dev/tasks/docker-tests/azure.linux.yml
+++ b/dev/tasks/docker-tests/azure.linux.yml
@@ -34,13 +34,7 @@ jobs:
inputs:
versionSpec: '3.8'
- - script: |
- git clone --no-checkout {{ arrow.remote }} arrow
- git -C arrow fetch -t {{ arrow.remote }} {{ arrow.branch }}
- git -C arrow checkout FETCH_HEAD
- git -C arrow submodule update --init --recursive
- git -C arrow remote add upstream https://github.com/apache/arrow.git
- displayName: Clone arrow
+ {{ macros.azure_checkout_arrow() }}
- script: pip install -e arrow/dev/archery[docker]
displayName: Setup Archery |
Also, we should ensure the build fails as soon as |
…r docker-tests We don't want to maintain multiple CI platforms to reduce maintenance cost.
…er-tests (#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: #41127 Authored-by: Sutou Kouhei <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
Issue resolved by pull request 41153 |
We use GitHub Actions instead of Azure Pipelines by #41153. So our jobs use the behavior now. |
…er-tests (#41153) We don't want to maintain multiple CI platforms to reduce maintenance cost. Use GitHub Actions for docker-tests. Yes. No. * GitHub Issue: #41127 Authored-by: Sutou Kouhei <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
…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 <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
…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 <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
…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 <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
…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 <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
…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 <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
…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 <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
Describe the bug, including details regarding any error messages, version, and platform.
Some azure jobs on the maintenance branch for 16.0.0 are currently failing to install archery with:
https://dev.azure.com/ursacomputing/crossbow/_build/results?buildId=62987&view=logs&j=50a69d0a-7972-5459-cdae-135ee6ebe312&t=e37d4d74-66f8-5ec4-c216-74b731c58e49&l=19
See maintenance validation PR with links to jobs here: #41118 (comment)
Component(s)
Archery, Continuous Integration
The text was updated successfully, but these errors were encountered: