Right now the rollup of status of test leaves is done based on which workflows have reported back.
It could happen that we want to run tests on gfx942 and gfx1100 but the runner for gfx1100 takes hours until it is triggered. In that case when all other running workflows have returned as "completed" the overall status would be finalized eventhough gfx1100 hasnt even run yet.
Some test suites are running workflow-dispatch, so there is no easy way to track via some orchestrator if all archs have finished or not. Other use workflow call - so there the orchestrater wraps around "all archs must have been processed we wanted to test".
Right now the rollup of status of test leaves is done based on which workflows have reported back.
It could happen that we want to run tests on gfx942 and gfx1100 but the runner for gfx1100 takes hours until it is triggered. In that case when all other running workflows have returned as "completed" the overall status would be finalized eventhough gfx1100 hasnt even run yet.
Some test suites are running workflow-dispatch, so there is no easy way to track via some orchestrator if all archs have finished or not. Other use workflow call - so there the orchestrater wraps around "all archs must have been processed we wanted to test".