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
CI is currently quite overloaded for new PRs. Can we reconsider the specific selection of tests that will be run for general PRs? This could involve improving the filters in the intelligent testing workflow, or simply reducing the matrix of tests.
The canary lane is now somewhat separated from the rest of intelligent testing. We should consider integrating this better.
Should we look at the functional tests and if they are still representative and covering our standard pipeline? or can we improve?
Are all tensorflow (smoke) tests still needed or can we reduce these?
One small addition, we may want a branch-scoped guard for dev pushes. Keeping CI on all commits for main is deliberate but the same choice may not hold for dev.
Activity
[-]Improve CI workflows[/-][+][Task] Improve CI workflows[/+]C-Achard commentedon Sep 15, 2026
One small addition, we may want a branch-scoped guard for
devpushes. Keeping CI on all commits formainis deliberate but the same choice may not hold fordev.