fix(ci): fix snapshot parity test and schedule it to be weekly #5373
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of changes
The snapshot parity test start failing since we move back to GH hosted runners due to insufficient RAM and disk space.
This PR moves it back to buildjet runners and schedule it weekly to reduce cost.
Successful test run: https://github.com/ChainSafe/forest/actions/runs/13650828365/job/38158739597?pr=5373
Issue on failure: #5374
Changes introduced in this pull request:
Reference issue to close (if applicable)
Closes
Other information and links
Change checklist