Integrated: 8374721: containers/docker/ShareTmpDir.java timed out after 8362087

[SendaoYan]

On Wed, 7 Jan 2026 13:53:59 GMT, SendaoYan <syan at openjdk.org> wrote:

> Hi all,
> 
> Sorry for the regression issue introduced by JDK-8362087. 
> 
> In the original code of JDK-8362087, before starting the first thread, a parameter was added to the global `DockerRunOptions` object, then the first Java thread was started, and within that thread, the first test Java process was launched. Immediately afterwards, a second parameter was added, and then a second Java thread was started, also launching a second test Java process. It was possible that when starting the second test Java process, the global `DockerRunOptions` object had already been assigned the second parameter, resulting in both test Java processes having identical parameters (two parameters each); whereas the original expectation was that the first Java process would have only one parameter, and the second would have two.
> 
> This PR fixed this bug. Adding the second parameter to the global `DockerRunOptions` object only after the first Java process has fully started ensures that both processes will have identical parameters.
> 
> Change has been verified locally on linux-x64 by run the test 100 times and all passed.

This pull request has now been integrated.

Changeset: 368de9ff
Author:    SendaoYan <syan at openjdk.org>
URL:       https://git.openjdk.org/jdk/commit/368de9ff2e46e4c66ee57b5fb961804c5d25c42a
Stats:     8 lines in 1 file changed: 5 ins; 0 del; 3 mod

8374721: containers/docker/ShareTmpDir.java timed out after 8362087

Reviewed-by: cnorrbin, sgehwolf

-------------

PR: https://git.openjdk.org/jdk/pull/29093