JDK-8255486 : Intermittent test failures in SandboxAppTest
  • Type: Bug
  • Component: javafx
  • Sub-Component: application-lifecycle
  • Affected Version: jfx16
  • Priority: P4
  • Status: Closed
  • Resolution: Won't Fix
  • Submitted: 2020-10-27
  • Updated: 2025-03-22
  • Resolved: 2025-03-22
Related Reports
Duplicate :  
JDK-8255126 - Intermittent test failures in SandboxAppTest
Relates :  
JDK-8255487 - Mark SandboxAppTest unstable on Windows
Relates :  
JDK-8246099 - Intermittent test failures in SandboxAppTest
Relates :  
JDK-8341090 - Remove support for security manager from JavaFX
Description
Even after the fix for JDK-8246099 I occasionally see these test failures on Windows:

> Task :systemTests:test

test.sandbox.SandboxAppTest > testFXApp FAILED
    java.lang.Exception: test timed out after 25000 milliseconds
        at java.base@15/java.lang.ProcessImpl.waitForInterruptibly(Native Method)
        at java.base@15/java.lang.ProcessImpl.waitFor(ProcessImpl.java:550)
        at app//test.sandbox.SandboxAppTest.runSandboxedApp(SandboxAppTest.java:70)
        at app//test.sandbox.SandboxAppTest.runSandboxedApp(SandboxAppTest.java:52)
        at app//test.sandbox.SandboxAppTest.testFXApp(SandboxAppTest.java:105)

test.sandbox.SandboxAppTest > testFXNonApp FAILED
    java.lang.Exception: test timed out after 25000 milliseconds
        at java.base@15/java.lang.ProcessImpl.waitForInterruptibly(Native Method)
        at java.base@15/java.lang.ProcessImpl.waitFor(ProcessImpl.java:550)
        at app//test.sandbox.SandboxAppTest.runSandboxedApp(SandboxAppTest.java:70)
        at app//test.sandbox.SandboxAppTest.runSandboxedApp(SandboxAppTest.java:52)
        at app//test.sandbox.SandboxAppTest.testFXNonApp(SandboxAppTest.java:110)

It rarely happens on a local system, but I frequently see it on our nightly test job.
Comments
This test was removed along with support for the security manager as part of JDK-8341090. It is no longer an issue for mainline, and not worth fixing for earlier release trains.
22-03-2025
The current timeout values seem more than sufficient. Until a solution can be found, we should probably mark the test as "UNSTABLE" on Windows.
27-10-2020