You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is now very unusual for all workflows to pass on first attempt, due to a variety of network/reliability issues. We should investigate ways to ensure that day-to-day development is not impacted as heavily by flakiness in the CI pipeline.
This could involve deferring some of the scope/number of workflows that are executed until some pre-release stage, or finding ways to make the workflows less dependent on flaky networks.
The text was updated successfully, but these errors were encountered:
Various improvements to CI workflows
- Compose all integ-test workflow executions into a single calling workflow
- Added a 'quick-check' workflow that provides faster feedback on branches other than main
- Only runs on ubuntu-latest
- Reuses cache entries from previous runs
- Builds distribution outputs so that these don't need to be committed during everyday development
- Added a workflow for purging old workflow executions
Together with the fix for #293, these changes fix#291
It is now very unusual for all workflows to pass on first attempt, due to a variety of network/reliability issues. We should investigate ways to ensure that day-to-day development is not impacted as heavily by flakiness in the CI pipeline.
This could involve deferring some of the scope/number of workflows that are executed until some pre-release stage, or finding ways to make the workflows less dependent on flaky networks.
The text was updated successfully, but these errors were encountered: