Intermittent `dotty.tools.dotc.CompilationTests.posCC` failure with `vulpix`

[github-actions]

See https://github.com/scala/scala3/actions/runs/14026446647

[Gedochao]

timing out on:

Test dotty.tools.dotc.CompilationTests.posCC failed: java.util.concurrent.TimeoutException: Compiling targets timed out, remaining targets: tests/pos-custom-args/captures/lazylists-exceptions.scala, tests/pos-custom-args/captures/capt-capability.scala, tests/pos-custom-args/captures/classes.scala, tests/pos-custom-args/captures/reaches.scala, tests/pos-custom-args/captures/i13816.scala, tests/pos-custom-args/captures/i20237-explicit.scala, tests/pos-custom-args/captures/capt-test.scala, tests/pos-custom-args/captures/filevar.scala, tests/pos-custom-args/captures/saferExceptions.scala, tests/pos-custom-args/captures/cc-dep-param.scala, tests/pos-custom-args/captures/i22723.scala, tests/pos-custom-args/captures/cc-poly-source-capability.scala, tests/pos-custom-args/captures/caseclass.scala, tests/pos-custom-args/captures/function-combinators.scala, tests/pos-custom-args/captures/colltest.scala, tests/pos-custom-args/captures/try.scala, tests/pos-custom-args/captures/path-use.scala, tests/pos-custom-args/captures/lazylists1.scala, captures/capt-separate, captures/byname-purefuns-adapt, captures/captureRef-separate-compilation, took 1200.027 sec
      at dotty.tools.vulpix.ParallelTesting$Test.executeTestSuite(ParallelTesting.scala:757)
      at dotty.tools.vulpix.ParallelTesting$CompilationTest.checkPass(ParallelTesting.scala:1264)
      at dotty.tools.vulpix.ParallelTesting$CompilationTest.checkCompile(ParallelTesting.scala:1185)
     at dotty.tools.dotc.CompilationTests.posCC(CompilationTests.scala:62)
     at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
     at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.lang.reflect.Method.invoke(Method.java:569)
      ...

cc @Linyxus @bracevac any recent capture checking changes which could be causing this?

[bracevac]

There is a flaky test that occasionally timeouts on the CI which so far has not been observed locally. @hamzaremmal and I are working on getting Vulpix to divulge which tests exactly cause the timeout. Damn those Pokemon creatures which can only utter their own names.

[Gedochao]

There is a flaky test that occasionally timeouts on the CI which so far has not been observed locally. @hamzaremmal and I are working on getting Vulpix to divulge which tests exactly cause the timeout. Damn those Pokemon creatures which can only utter their own names.

@bracevac do we have another issue to track that? if not, let's use this ticket. Assigning both of you, so we don't lose track of it.