Skip to content
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

Closed
raulcd opened this issue Apr 10, 2024 · 4 comments
Closed

Comments

@raulcd
Copy link
Member

raulcd commented Apr 10, 2024

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:

pip install -e arrow/dev/archery[docker]
========================== Starting Command Output ===========================
/usr/bin/bash --noprofile --norc /home/vsts/work/_temp/8c33e1f6-f05d-42a3-b425-f289fff01a2a.sh
ERROR: arrow/dev/archery[docker] is not a valid editable requirement. It should either be a path to a local project or a VCS URL (beginning with bzr+http, bzr+https, bzr+ssh, bzr+sftp, bzr+ftp, bzr+lp, bzr+file, git+http, git+https, git+ssh, git+git, git+file, hg+file, hg+http, hg+https, hg+ssh, hg+static-http, svn+ssh, svn+http, svn+https, svn+svn, svn+file).

[notice] A new release of pip is available: 23.0.1 -> 24.0
[notice] To update, run: pip install --upgrade pip

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

@raulcd raulcd added the Priority: Blocker Marks a blocker for the release label Apr 10, 2024
@raulcd raulcd added this to the 16.0.0 milestone Apr 10, 2024
@kou
Copy link
Member

kou commented Apr 10, 2024

Hmm. It seems that git clone failed:

https://dev.azure.com/ursacomputing/crossbow/_build/results?buildId=62987&view=logs&j=50a69d0a-7972-5459-cdae-135ee6ebe312&t=344e7f7d-9526-5715-882a-1f0e8858127b&l=13

fatal: couldn't find remote ref maint-16.0.0
error: pathspec 'FETCH_HEAD' did not match any file(s) known to git

Could you try this on maint-16.0.0?

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

@pitrou
Copy link
Member

pitrou commented Apr 11, 2024

Also, we should ensure the build fails as soon as git clone fails, not later with an unrelated error message.

kou added a commit to kou/arrow that referenced this issue Apr 11, 2024
…r docker-tests

We don't want to maintain multiple CI platforms to reduce maintenance
cost.
kou added a commit that referenced this issue Apr 12, 2024
…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]>
@kou
Copy link
Member

kou commented Apr 12, 2024

Issue resolved by pull request 41153
#41153

@kou kou closed this as completed Apr 12, 2024
@kou
Copy link
Member

kou commented Apr 12, 2024

Also, we should ensure the build fails as soon as git clone fails, not later with an unrelated error message.

We use GitHub Actions instead of Azure Pipelines by #41153. So our jobs use the behavior now.

raulcd pushed a commit that referenced this issue Apr 12, 2024
…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]>
vibhatha pushed a commit to vibhatha/arrow that referenced this issue Apr 15, 2024
…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]>
tolleybot pushed a commit to tmct/arrow that referenced this issue May 2, 2024
…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]>
tolleybot pushed a commit to tmct/arrow that referenced this issue May 4, 2024
…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]>
rok pushed a commit to tmct/arrow that referenced this issue May 8, 2024
…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]>
rok pushed a commit to tmct/arrow that referenced this issue May 8, 2024
…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]>
vibhatha pushed a commit to vibhatha/arrow that referenced this issue May 25, 2024
…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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants