Concurrent trybuild tests lead to artifact name conflicts

[sandersaares]

I am seeing test result anomalies accompanied by such messages:

STDERR:
┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈
error: no bin target named `trybuild001`

Did you mean `trybuild000`?
┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈

We have multiple test functions that invoke trybuild. My interpretation of the situation is that the trybuild test artifacts end up as `target\tests\trybuild\x86_64-pc-windows-msvc\debug\trybuild000.exe" and it sounds like in our case they are conflicting between different trybuild tests, each of which try to build artifacts with the same indexes.

Is there an intentional limitation where only the pattern with a single #[test] fn ui { ... } is supported? If so, I suggest documenting this.

[neysofu]

My team has also experienced this. Occasionally, our trybuild tests fail with the error message that you reported.