-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
P4
-
Affects Version/s: jfx25
-
Component/s: javafx
-
os_x
We started seeing the following failure:
StageFocusTest > testStageHasFocusAfterShow(Stage) > [1] javafx.stage.Stage@463b4ac8 FAILED
org.opentest4j.AssertionFailedError: Stage.isFocused() returned false! Stage does not have focus after showing. Some tests might fail because of this. Try re-running the tests with '--no-daemon' flag in Gradle. ==> expected: <true> but was: <false>
at app//org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
at app//org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
at app//org.junit.jupiter.api.AssertTrue.failNotTrue(AssertTrue.java:63)
at app//org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:36)
at app//org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:214)
at app//test.robot.javafx.stage.StageFocusTest.testStageHasFocusAfterShow(StageFocusTest.java:195)
This happens on Intel macOS 14 and using JDK 26. We didn't see it yet on JDK 25 or other hardware, but it might just happen to intermittently show up there.
StageFocusTest > testStageHasFocusAfterShow(Stage) > [1] javafx.stage.Stage@463b4ac8 FAILED
org.opentest4j.AssertionFailedError: Stage.isFocused() returned false! Stage does not have focus after showing. Some tests might fail because of this. Try re-running the tests with '--no-daemon' flag in Gradle. ==> expected: <true> but was: <false>
at app//org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
at app//org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
at app//org.junit.jupiter.api.AssertTrue.failNotTrue(AssertTrue.java:63)
at app//org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:36)
at app//org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:214)
at app//test.robot.javafx.stage.StageFocusTest.testStageHasFocusAfterShow(StageFocusTest.java:195)
This happens on Intel macOS 14 and using JDK 26. We didn't see it yet on JDK 25 or other hardware, but it might just happen to intermittently show up there.