Affected version
3.6.0
Bug description
Surefire 3.6.0 initialises the fork's NIO/native networking layer before applying systemPropertyVariables, so any property read during that initialisation — like java.net.preferIPv4Stack — arrives too late. If a project uses systemPropertyVariables, the failure is silent and environment-dependent.
I encountered this bug upgrading the pluging in hadoop, that uses the variable preferIPv4Stack but the fork initializes the IPv6 Stack ignoring the variable.
Found working in HADOOP-19964 :https://issues.apache.org/jira/browse/HADOOP-19964
I use AI assistance to perform the coding work.
Affected version
3.6.0
Bug description
Surefire 3.6.0 initialises the fork's NIO/native networking layer before applying systemPropertyVariables, so any property read during that initialisation — like java.net.preferIPv4Stack — arrives too late. If a project uses systemPropertyVariables, the failure is silent and environment-dependent.
I encountered this bug upgrading the pluging in hadoop, that uses the variable preferIPv4Stack but the fork initializes the IPv6 Stack ignoring the variable.
Found working in HADOOP-19964 :https://issues.apache.org/jira/browse/HADOOP-19964
I use AI assistance to perform the coding work.