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
{{ message }}
This repository has been archived by the owner on Mar 21, 2024. It is now read-only.
Some elements of our PR build pipeline take a long time to run and very rarely fail. This slows down the PR process substantially. We should prune those out and make a daily build which would run on main, and if it took an age that would not matter. Any errors picked up by the daily build would then become high priority issues for us to fix.
It's important to ensure all training completes as expected before allowing merges. IMO anything < 30 mins for a PR build is acceptable. Better to merge good code slowly than have to hotfix bad code quickly.
Some elements of our PR build pipeline take a long time to run and very rarely fail. This slows down the PR process substantially. We should prune those out and make a daily build which would run on main, and if it took an age that would not matter. Any errors picked up by the daily build would then become high priority issues for us to fix.
AB#4257
The text was updated successfully, but these errors were encountered: