-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nightly Dotty workflow of 2022-01-24 failed #14332
Comments
Duplicates the failures earlier at #13367 which I assumed to be spurious because everything else was green and this passed locally. Though frankly, still difficult to know the canonical way to run a given test. I re-read the contributing page to little avail.
Probably this was meant to be a failed test, where the embedded source string does not compile:
|
Maybe the test run of the breaking merge is green because it ran on
|
741e17e is the first commit where there is no warning in type M[X] = X match { case Int => String case _ => Int } |
The warning was removed in scala#12261 Fixes scala#14332
@philwalk see the |
Sorry for the delay responding, I'll look into it. |
I have a fix for @test |
@philwalk in the sense that committed PRs are done deals unless reverted, the usual course is just to look to the future and open new PRs. I'm curious to see if the test was supposed to fail, it's a cliff-hanger! |
The warning was removed in scala#12261 Fixes scala#14332
See https://github.com/lampepfl/dotty/actions/runs/1737834571
The text was updated successfully, but these errors were encountered: