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

[Archery][CI] Fix possible race condition when submitting crossbow builds #31703

Closed
asfimport opened this issue Apr 25, 2022 · 2 comments
Closed

Comments

@asfimport
Copy link

Sometimes when trying to use github-actions to submit crossbow jobs an error is raised like:

Failed to push updated references, potentially because of credential issues: ['refs/heads/actions-1883-github-wheel-windows-cp310-amd64', 'refs/tags/actions-1883-github-wheel-windows-cp310-amd64', 'refs/heads/actions-1883-github-wheel-windows-cp39-amd64', 'refs/tags/actions-1883-github-wheel-windows-cp39-amd64', 'refs/heads/actions-1883-github-wheel-windows-cp37-amd64', 'refs/tags/actions-1883-github-wheel-windows-cp37-amd64', 'refs/heads/actions-1883-github-wheel-windows-cp38-amd64', 'refs/tags/actions-1883-github-wheel-windows-cp38-amd64', 'refs/heads/actions-1883']
The Archery job run can be found at: https://github.com/apache/arrow/actions/runs/2195038965

As discussed on this github comment (#12930 (comment)

We should remove the auto incremented IDs entirely and use unique hashes instead, e.g.: actions--github-wheel-windows-cp310-amd64 instead of actions-1883-github-wheel-windows-cp310-amd64. Then we wouldn't need to fetch the new references either, making remote crossbow builds and local submission much quicker.

The error can also be seen here: #12987 (comment)

Reporter: Raúl Cumplido / @raulcd
Assignee: Raúl Cumplido / @raulcd

PRs and other links:

Note: This issue was originally created as ARROW-16317. Please see the migration documentation for further details.

@asfimport
Copy link
Author

Raúl Cumplido / @raulcd:
cc - @assignUser  

@asfimport
Copy link
Author

Krisztian Szucs / @kszucs:
Issue resolved by pull request 13188
#13188

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

2 participants