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
Add method to ignore unstable checker framework violations. #12210
Comments
If it is always |
We got a new one |
Or for unstable errors, we could just remove any numbers (just while comparing) present in |
lets remove details for now, to make fix quicker. |
Fix is merged |
From https://github.com/checkstyle/checkstyle/actions/runs/3074040335/jobs/4966560151
link to Suppression :
checkstyle/.ci/checker-framework-suppressions/checker-framework-nullness-optional-interning-suppressions.xml
Lines 2963 to 2973 in 6335dd8
checkstyle/.ci/checker-framework-suppressions/checker-framework-nullness-optional-interning-suppressions.xml
Lines 3404 to 3414 in 6335dd8
These errors are unstable because
capture#
keeps changing with every run. Although these errors are present in the current suppression model asunstable = "true"
but it does not work because unlike pitest unstable suppression model, here the content of the error changes.Another one is:
checkstyle/.ci/checker-framework-suppressions/checker-framework-methods-resource-fenum-suppressions.xml
Lines 80 to 89 in 6335dd8
Here
temp-var-\d+
keeps on changing, this field is present inMessage:
The text was updated successfully, but these errors were encountered: