we've found two items related to

--[no-]fast

that we'll probably want to try and fix as part of

1.25.x

... i'll see if i can get patches out for them today.

Cool, thanks. Do you know what the issues are?

1) coverage isn't merged across targets, 2) "test specs" in junit fail if any of multiple targets don't match, which is likely if you run for more than one target.

Ah, I think I ran into both of these with the Junit tests and wasn’t clear how to fix them.. Do they sound fixable?

yea... just a pain in the butt

Worst case, Toolchain would be okay with reverting the PR. We only were doing it as a courtesy to try to make the V1 migration to V2 smoother for users, but don’t have any particular use case for it

i think we're in the long tail at this point. and we can set

--fast

for now in each of these locations.