Open mashehu opened 6 days ago
I wouldn't at special paths just all modules and subworkflows. Then the filter step will take care of only picking up GPU tests
why aren't some tests not launching ?
they are not stalled, they are just required, but never launched (because we don't have anything to test). so we need to remove them from the ruleset and add a step which confirms the passing of all tests (either that they ran successfully or that they didn't have to be run)
in
gpu-tests.yml
, the trigger is on PR to master and those paths. should we include subworkflows too that have gpu tests ?