-
-
Notifications
You must be signed in to change notification settings - Fork 375
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
Capture GitCommandError
in log file
#1232
Conversation
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.
Looks good - we'll have to see if this reveals anything interesting.
Got an HTTP 429 today....
https://github.com/beeware/briefcase/actions/runs/5073634768/jobs/9113045436 |
HTTP429 is a fun one... I wonder if our CI behavior is indistinguishable from a bot attack... |
yeah....although, if we force the caches to refresh more often, we could probably largely mitigate the negative outcomes from this....maybe just put the month and year on the cache like we did for winstore Python caches. |
Changes
git
failures in the log fileExample of new log entry
PR Checklist: