Raúl Cumplido created ARROW-16317:
-------------------------------------

             Summary: [Archery][CI] Fix possible race condition when submitting 
crossbow builds
                 Key: ARROW-16317
                 URL: https://issues.apache.org/jira/browse/ARROW-16317
             Project: Apache Arrow
          Issue Type: Bug
          Components: Archery, Continuous Integration
            Reporter: Raúl Cumplido
             Fix For: 9.0.0


Sometimes when trying to use github-actions to submit crossbow jobs an error is 
raised like:
{code:java}
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{code}
As discussed on this github comment 
([https://github.com/apache/arrow/pull/12930#issuecomment-1103772507)]

We should remove the auto incremented IDs entirely and use unique hashes 
instead, e.g.: actions-<short-hash>-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: 
https://github.com/apache/arrow/pull/12987#issuecomment-1108516668



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to