-
Notifications
You must be signed in to change notification settings - Fork 21
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
Warning is not suppressed after error despite -Wconf
#12587
Comments
This rings a bell, I think I noticed this issue when working on the Scala 3 port, but then dropped the ball I guess... |
This partest only errors, so it is more subtle.
|
Actually The test has a OK, Normally, Why doesn't my partest show the reported behavior? Because the default
so the deprecation is only summarized. Does that imply that partest compilation does not summarize? No, So why does the junit compile show the warning?
turns on deprecation and also sets |
Reproduction steps
Scala version: 2.13.8
Problem
The warning is suppressed by configuration, but if there is an error (as shown, for example), the warning is emitted.
Now I'm not sure I didn't add suppressions because of this behavior, even though suppressions were already configured.
(It's also unfortunate that the error report is "old school", reporting on the innocent line because that is when the parser noticed it, instead of on the guilty line.)
The text was updated successfully, but these errors were encountered: