You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following issue code already exists in the test CI, but it does not cause the CI to fail.
For example:
2022-07-20T11:31:07.9036071Z [info] Test dotty.tools.dotc.FromTastyTests.runTestFromTasty started
2022-07-20T11:33:09.2040111Z No tests available under target - erroneous test?
2022-07-20T11:33:09.8939791Z [info] Test dotty.tools.dotc.FromTastyTests.posTestFromTasty started
2022-07-20T11:35:11.2843408Z No tests available under target - erroneous test?
I am not sure about the CI. I think that one file in the test should be run with version 3.0.2, that's why it has this funny name. Anyway, under 3.2 this code does not compile (nor should it).
I am not sure about the CI. I think that one file in the test should be run with version 3.0.2, that's why it has this funny name. Anyway, under 3.2 this code does not compile (nor should it).
Oh, I thought it should, and I was not aware of that file name convention. Now it makes sense.
The following issue code already exists in the test CI, but it does not cause the CI to fail.
For example:
As a result, we missed a regression.
See
tests/run/backwardsCompat-implicitParens/A_1_c3.0.2.scala
Related to the work done in #14840 and followed by #15679 (the last probably introduced the regression)
Compiler version
v3.2.0-RC4
Minimized code
Output
Expectation
No error, and the CI should be fixed that this error reflects in the underlying CI fail/success indication.
The text was updated successfully, but these errors were encountered: