-
-
Notifications
You must be signed in to change notification settings - Fork 31k
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
Implement retry on checkout for reusable-ubuntu #129241
base: main
Are you sure you want to change the base?
Conversation
@@ -34,9 +34,12 @@ jobs: | |||
PYTHONSTRICTEXTENSIONBUILD: 1 | |||
TERM: linux | |||
steps: | |||
- uses: actions/checkout@v4 | |||
- uses: Wandalen/wretry.action@master |
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.
Is there a feature request for actions/checkout
to retry checkouts?
I'm unsure about using a third party action here, vs e.g. a run:
block just using git
commands.
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.
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.
Raised: actions/checkout#2048
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.
Re: https://github.com/diegorusso/cpython/actions/runs/12948283932/job/36116629838#step:4:157
That's just the third-party linter that complaining about something that either doesn't exist or hasn't been added to the linter's schema.
Please could you rename your branch to 3.14-test-retry
so it will trigger some jobs that use actions/checkout?
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.
Same thing: https://github.com/diegorusso/cpython/actions/runs/12949425398
BTW also the GitHub editor was complaining about the retry.
![Screenshot 2025-01-24 at 12 17 09](https://private-user-images.githubusercontent.com/342108/406432014-f66ece7c-fcf9-4dd1-b449-8faaa53ea9a4.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg3ODY0NTMsIm5iZiI6MTczODc4NjE1MywicGF0aCI6Ii8zNDIxMDgvNDA2NDMyMDE0LWY2NmVjZTdjLWZjZjktNGRkMS1iNDQ5LThmYWFhNTNlYTlhNC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjA1JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIwNVQyMDA5MTNaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0zMjM3MmNlMDMxOGEyNjY4M2U2YTZiYjE4MDE3NGFiMWQ1MDJjZTEzYjM0OTUzNjE0YTMyY2ViNGZiMTc0NjFkJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.ANBbI2AxQgrVURnK1_PnbPmRmPh5CM6ONhipvgA1yIQ)
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.
Thanks, and there it is on test.yml
:
Invalid workflow file: .github/workflows/build.yml#L258
The workflow is not valid. In .github/workflows/build.yml (Line: 258, Col: 11): Error from called workflow diegorusso/cpython@6a298de (Line: 40, Col: 7): Unexpected value 'retry'
https://github.com/diegorusso/cpython/actions/runs/12949425427
It does look like actions/checkout does have a non-configurable 3-attempt retry already built-in:
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.
I think here we are looking at this from the wrong angle. If you see the failures posted initially, they don't fail while checking out the repo.
It is not started at all. After it prints the env variable there is nothing. I have the feeling that there is some infrastructure issue in running that action on a specific node.
Even if we put the retry 100 times, they won't be executed as this fails even before to start the process.
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.
Yes, that's the impression I get too.
Looking more closely at the raw logs (https://github.com/python/cpython/actions/runs/12934438169/job/36075486419?pr=129232 > ⚙️ > View raw logs), the checkout does actually succeed.
For some reason, the next step just doesn't start.
Comparing with a passing build:
![image](https://private-user-images.githubusercontent.com/1324225/406459781-d058930c-7541-4638-80e3-bb718b039cdc.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg3ODY0NTMsIm5iZiI6MTczODc4NjE1MywicGF0aCI6Ii8xMzI0MjI1LzQwNjQ1OTc4MS1kMDU4OTMwYy03NTQxLTQ2MzgtODBlMy1iYjcxOGIwMzljZGMucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIwNSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMDVUMjAwOTEzWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NDU0NTIyYjNlYjM5MTg2ZjQxMTdjMjNhYTIyMWZhMTZlOGQ3Nzk5ZGExOThjN2NiMjA3M2Q5NmQzNjI3ZjNhNSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.8fE3LR-Dw6n3gNHB6VEWvhczxGSr7dapfv47-QHHe4c)
(Not shown in the diff, the last line of the failing build is:)
2025-01-23T17:13:58.8145851Z Cleaning up orphan processes
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.
Oh wow, I didn't remember that we had access to these raw logs. They are useful indeed.
So the retry is pointless because it actually doesn't fail on the checkout.
Do you know what the actual error is here? There's not much in the logs. |
Not yet. @ambv has enabled debug information so next time that happens hopefully we will know what is going on. |
I have a 404 on the link. |
There are a few occasions where the checkout on reusable-ubuntu is failing. This happens on Ubuntu arm for free threading builds. Examples:
The retry mechanism should protect us from a failure.