Issue #16937: Resolve all pitest CIs fails#16945
Conversation
| - name: Generate pitest-${{ matrix.profile }} report | ||
| run: | | ||
| ./.ci/pitest.sh "pitest-${{ matrix.profile }}" | ||
| ./.ci/pitest.sh "pitest-${{ matrix.profile }}" -DargLine="--add-opens java.base/java.lang=ALL-UNNAMED" |
There was a problem hiding this comment.
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.codehaus.groovy.reflection.CachedClass (file:/usr/share/groovy/lib/groovy-2.4.21.jar) to method java.lang.Object.finalize()
WARNING: Please consider reporting this to the maintainers of org.codehaus.groovy.reflection.CachedClass
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
New surviving mutation(s) found:
Source File: "PackageNamesLoader.java"
Class: "com.puppycrawl.tools.checkstyle.PackageNamesLoader"
Method: "processFile"
Line Contents: "throw new CheckstyleException("unable to open " + packageFile, ex);"
Mutator: "org.pitest.mutationtest.engine.gregor.mutators.NonVoidMethodCallMutator"
Description: "removed call to java/lang/String::valueOf"
Line Number: 180
The warning and surviving mutations do not appear locally, but they do show up in the GitHub workflow.
By adding this argument to the pitest.yml workflow, the JVM permits reflective access, suppressing the warning during PITest runs on GitHub Actions.
But I'm not sure it will kill the surviving mutation; I'm just trying to solve this problem.
|
Updating this single line is not at all fix to what we been going through As all mutations will not be killed and cleaned from whole repo pitest ci will fail, i am working on it, almost there as i am having exams after 2hrs i will be providing final updates pitest ci passing PR soon. |
I appreciate your response, but I did not state that this change would eliminate the surviving mutation. I was trying to solve this problem. |
Totally appreciated!! No worries everyone trying their best from there side to fix it. |
Resolve #16937