Skip to content

Commit e2778f6

Browse files
committed
Go back to JDK 11 for mutation tests
When running the mutation tests in JDK 17, they seem to incorrectly report lower coverage than what is actually the case - including whole classes plummeting to 0% coverage. I have manually confirmed that some of the mutations reported as uncovered are in fact covered by the tests. Perhaps there's some test discovery mechanism that breaks in JDK 17; I'll have to test newer versions of the test frameworks and see if that helps.
1 parent 9de5b72 commit e2778f6

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

.github/workflows/coverage.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,10 +18,10 @@ jobs:
1818
- name: Check out code
1919
uses: actions/checkout@v3
2020

21-
- name: Set up JDK 11
21+
- name: Set up JDK
2222
uses: actions/setup-java@v3
2323
with:
24-
java-version: 17
24+
java-version: 11
2525
distribution: temurin
2626

2727
- name: Run mutation test

0 commit comments

Comments
 (0)