Fix surefire warnings in build #2106
Conversation
akurtakov
force-pushed
the
master
branch
2 times, most recently
from
914ab70 to
ddd2b70
Compare
Test Results 539 files ±0 539 suites ±0 31m 5s ⏱️ - 3m 9s For more details on these failures, see this check. Results for commit eeae96a. ± Comparison against base commit 48cbec2. ♻️ This comment has been updated with latest results. |
Remove the override in jenkinsfile so the default is not overriden. Fixes following warnings in the build: ``` [WARNING] useSystemClassLoader setting has no effect when not forking [WARNING] The parameter forkCount should likely not be 0. Forking a JVM for tests improves test accuracy. Ensure to have a <forkCount> >= 1. ```
|
Windows test failure is in master for long time. @HeikoKlare @fedejeanne What is the plan for this windows test failure? If there is none I'll disable it on Monday. |
It was a a sporadically failing test for a while (only failing in GHA). It just started to fail rather consistently on Jenkins. It was not reproducible locally. I was now able to reproduce it on a system with a recent Windows build, so might be that we are now able to fix it via local reproduction. I added information in #1843. |
Fixes following warnings in the build: