-
Notifications
You must be signed in to change notification settings - Fork 39
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
Checkstyle errors reported multiple times by Error Prone parser #34
Comments
I'm not really sure how this should be solved. Same with Checkstyle. If that is the output, then the lib is doing what it should. Is this not more of an issue about making Error Prone not print Checkstyle errors? |
Are you sure that ErrorProne is outputting the checkstyle errors? I think is just the checkstyle task ( This is the full build log:
|
Ok, I see. You are right. But the Error Prone parser is fragile. The correct way of fixing this would be to solve: google/error-prone#444 You can up-vote or comment that one if you like =) |
Sure, I had already given a 👍 to your message, but I just added also a comment to make it more clear. Regarding this issue, what about ignoring all the errors that contain string "checkstyle" in them? I don't think this string should appear in any ErrorProne error, unless you are building some code that has it in the source itself, and should not be that common imho. What to you think? |
It feels like a bumpy road to go down... Perhaps you can replace it yourself before parsing the output with the lib? https://stackoverflow.com/questions/5410757/delete-lines-in-a-text-file-that-contain-a-specific-string |
Thanks, this could be a workaround for me :) But consider maybe the opposite approach of what I have suggested: check if the error don't contain the string "errorprone.info" on them. All the official ErrorProne errors have them at the end:
And with this logic you can support error prone plugins just checking for other keywords. For example for NullAway it will be "uber.com/nullaway":
|
Currently the Error Prone parser is reporting also the checkstyle errors. This is a problem for 2 reasons:
This mean that if I have 1 error and 2 variants I get 3 reports of the same error (and with 3 errors and 5 variants I get 18 reports where only 3 are unique errors and the rest are just duplicates).
Checkstyle build output:
Full build source: https://travis-ci.org/leinardi/FloatingActionButtonSpeedDial/builds/365085225?utm_source=github_status&utm_medium=notification
The text was updated successfully, but these errors were encountered: