Skip to content

StatusDialogManagerTest.testBug275867() flaky in Windows I-Builds #3717

@HeikoKlare

Description

@HeikoKlare

The test case org.eclipse.ui.tests.statushandlers.StatusDialogManagerTest.testBug275867() sporadically fails in I-Builds on Windows:

Dialog is not centered correctly expected:<Point {254, 102}> but was:<Point {254, 103}>

java.lang.AssertionError: Dialog is not centered correctly expected:<Point {254, 102}> but was:<Point {254, 103}>
at org.junit.Assert.fail(Assert.java:89)
at org.junit.Assert.failNotEquals(Assert.java:835)
at org.junit.Assert.assertEquals(Assert.java:120)
at org.eclipse.ui.tests.statushandlers.StatusDialogManagerTest.testBug275867(StatusDialogManagerTest.java:777)
at java.base/java.lang.reflect.Method.invoke(Method.java:580)

From the values, it might be some rounding issue related to HiDPI support / monitor-specific scaling.
As an initial thought if we cannot reproduce the fail locally or have any other clue: we might add debug output with the actual and expected values to the test, such that we know how the values differ in case the test succeeds. It would be strange if in case of a success the values are the exact same as we see in case of a failure (except for the off-by-one), as there should be no non-determinism in how values are calculated/rounded. That's why I would expect the values to be completely different in case of a success, which could be verified by debug output.

Metadata

Metadata

Assignees

No one assigned

    Labels

    WindowsHappens on Windows OStestjunit test related things

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions