-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Corpus Testing Bugfixes #5085
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
base: master
Are you sure you want to change the base?
Corpus Testing Bugfixes #5085
Conversation
We've introduced a timeout to the analyze_binaries job to prevent the accidental overuse of GitHub Actions minutes in the future. The retries variable was missing and so the number of retries was empty and never being evaluated. Lastly, we update the gh_push_file.sh script to be smarter about retriable conditions.
…EN env var convention
…ter-timeouts
Thank you!
Do you think hosting the content elsewhere (e.g., an HTTP server that we control) is a better solution? |
Yeah, I think that could work. You really just need to be able to push/pull the snapshots from somewhere. |
Several bugs are addressed in the corpus testing framework.
gh_push_file.sh
to determine what errors can be safely recovered from short-circuiting otherwisetimeou 8000 t-minutes
setting (30 minutes at most per file) to theanalyze_binaries
job$ANALYZE_SNAPSHOT_RETRIES
variable that was causing the[: 12: unary operator expected
errorTEMP_DIR
toSNAPSHOT_DIR
insnapshot_diff.sh
gh_ls.sh
script was mistakenly being called to enumerate files in the master/main branch due to a missing-b ${REF_HEAD}
option that has now been added. There shouldn’t be any more file discrepancies within the snapshot branchGH_TOKEN
overGITHUB_TOKEN
is being appliedactionlint
,action-validator
,shellcheck
,shfmt
Items that remain to be addressed: