Suppress the parallel warning during coverage calculation

As we properly serialize the coverage calculation, the warning that is logged after detecting multiple threads can be suppressed.
pitest · May 19, 2023 · 3138d20 · 3138d20
1 parent b1ffc1f
commit 3138d20
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/pom.xml b/pom.xml
@@ -23,7 +23,7 @@
 		<junit.platform.version>1.9.2</junit.platform.version>
 		<junit.version>5.9.2</junit.version>
 		<mockito.version>2.7.6</mockito.version>
-		<pitest.version>1.9.0</pitest.version>
+		<pitest.version>1.13.2</pitest.version>
 		<cucumber.version>5.0.0</cucumber.version>
 		<spock.version>2.3-groovy-4.0</spock.version>
 		<junit4.version>4.13.2</junit4.version>

diff --git a/src/main/java/org/pitest/junit5/JUnit5TestUnitFinder.java b/src/main/java/org/pitest/junit5/JUnit5TestUnitFinder.java
@@ -191,7 +191,7 @@ public void executionStarted(TestIdentifier testIdentifier) {
                         lock(testIdentifier);
                     }
 
-                    l.executionStarted(new Description(testIdentifier.getUniqueId(), testClass));
+                    l.executionStarted(new Description(testIdentifier.getUniqueId(), testClass), true);
                     identifiers.add(testIdentifier);
                 }
                 return;
@@ -211,7 +211,7 @@ && hasMethodSource(testIdentifier)
                     parentCoverageSerializers.put(testIdentifier.getUniqueIdObject(), new AtomicReference<>());
                 }
 
-                l.executionStarted(new Description(testIdentifier.getUniqueId(), testClass));
+                l.executionStarted(new Description(testIdentifier.getUniqueId(), testClass), true);
                 identifiers.add(testIdentifier);
             }
         }