-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Random failing VirtualTableViewerTest.testRenameWithSorter and VirtualTableViewerTest.testContains #1005
Labels
Comments
HeikoKlare
changed the title
Random failing VirtualTableViewerTest.testRenameWithSorter
Random failing VirtualTableViewerTest.testRenameWithSorter and VirtualTableViewerTest.testContains
Sep 12, 2023
The test
|
This was referenced Oct 17, 2023
Seems to fails all the time on Mac. @sratz could you have a look if this can be fixed or if it should be disabled on Mac? |
This was referenced Nov 30, 2023
Merged
Merged
also reported in #1283 |
jukzi
pushed a commit
to jukzi/eclipse.platform.ui
that referenced
this issue
Dec 7, 2023
move "fViewer.getControl().update();" to front eclipse-platform#1005
jukzi
pushed a commit
to jukzi/eclipse.platform.ui
that referenced
this issue
Dec 7, 2023
move "fViewer.getControl().update();" to front eclipse-platform#1005
This was referenced Feb 8, 2024
This was referenced Apr 3, 2024
This was referenced Apr 18, 2024
HeikoKlare
added a commit
to HeikoKlare/eclipse.platform.ui
that referenced
this issue
Apr 29, 2024
…ipse-platform#1005 Several test cases of VirtualTableViewerTest randomly fail. This includes explicit failures of testRenameWithSorter() and testContains() and silent failures of other test cases that simply return successfully even if the test actually failed. The reason is a missing processing of an update of the table data, which is most likely caused by the shell not having focus. With this change, the test execution ensures that in cases where an update of the table data is expected, the shell is forced active. In addition, early returns producing silent failures are replaced by assertions leading to explicit failures in case the condition is still not met. Contributes to eclipse-platform#1583 May fix eclipse-platform#1005
HeikoKlare
added a commit
to HeikoKlare/eclipse.platform.ui
that referenced
this issue
Apr 29, 2024
…ipse-platform#1005 Several test cases of VirtualTableViewerTest randomly fail. This includes explicit failures of testRenameWithSorter() and testContains() and silent failures of other test cases that simply return successfully even if the test actually failed. The reason is a missing processing of an update of the table data, which is most likely caused by the shell not having focus. With this change, the test execution ensures that in cases where an update of the table data is expected, the shell is forced active. In addition, early returns producing silent failures are replaced by assertions leading to explicit failures in case the condition is still not met. Contributes to eclipse-platform#1583 May fix eclipse-platform#1005
HeikoKlare
added a commit
to HeikoKlare/eclipse.platform.ui
that referenced
this issue
Apr 29, 2024
…ipse-platform#1005 Several test cases of VirtualTableViewerTest randomly fail. This includes explicit failures of testRenameWithSorter() and testContains() and silent failures of other test cases that simply return successfully even if the test actually failed. The reason is a missing processing of an update of the table data, which is most likely caused by the shell not having focus. With this change, the test execution ensures that in cases where an update of the table data is expected, the shell is forced active. In addition, early returns producing silent failures are replaced by assertions leading to explicit failures in case the condition is still not met. Contributes to eclipse-platform#1583 May fix eclipse-platform#1005
HeikoKlare
added a commit
to HeikoKlare/eclipse.platform.ui
that referenced
this issue
Apr 29, 2024
…ipse-platform#1005 Several test cases of VirtualTableViewerTest randomly fail. This includes explicit failures of testRenameWithSorter() and testContains() and silent failures of other test cases that simply return successfully even if the test actually failed. The reason is a missing processing of an update of the table data, which is most likely caused by the shell not having focus. With this change, the test execution ensures that in cases where an update of the table data is expected, the shell is forced active and events are processed until the data is finally set properly. In addition, early returns producing silent failures are replaced by assertions leading to explicit failures in case the condition is still not met. Contributes to eclipse-platform#1583 May fix eclipse-platform#1005
HeikoKlare
added a commit
to HeikoKlare/eclipse.platform.ui
that referenced
this issue
Apr 29, 2024
…ipse-platform#1005 Several test cases of VirtualTableViewerTest randomly fail. This includes explicit failures of testRenameWithSorter() and testContains() and silent failures of other test cases that simply return successfully even if the test actually failed. The reason is a missing processing of an update of the table data, which is most likely caused by the shell not having focus. With this change, the test execution ensures that in cases where an update of the table data is expected, the shell is forced active and events are processed until the data is finally set properly. In addition, early returns producing silent failures are replaced by assertions leading to explicit failures in case the condition is still not met. Contributes to eclipse-platform#1583 May fix eclipse-platform#1005
HeikoKlare
added a commit
to HeikoKlare/eclipse.platform.ui
that referenced
this issue
May 1, 2024
…ipse-platform#1005 Several test cases of VirtualTableViewerTest randomly fail. This includes explicit failures of testRenameWithSorter() and testContains() and silent failures of other test cases that simply return successfully even if the test actually failed. The reason is a missing processing of an update of the table data, which is most likely caused by the shell not having focus. With this change, the test execution ensures that in cases where an update of the table data is expected, the shell is forced active and events are processed until the data is finally set properly. In addition, early returns producing silent failures are replaced by assertions leading to explicit failures in case the condition is still not met. Contributes to eclipse-platform#1583 May fix eclipse-platform#1005
HeikoKlare
added a commit
that referenced
this issue
May 1, 2024
Several test cases of VirtualTableViewerTest randomly fail. This includes explicit failures of testRenameWithSorter() and testContains() and silent failures of other test cases that simply return successfully even if the test actually failed. The reason is a missing processing of an update of the table data, which is most likely caused by the shell not having focus. With this change, the test execution ensures that in cases where an update of the table data is expected, the shell is forced active and events are processed until the data is finally set properly. In addition, early returns producing silent failures are replaced by assertions leading to explicit failures in case the condition is still not met. Contributes to #1583 May fix #1005
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The test
org.eclipse.jface.tests.viewers.VirtualTableViewerTest.testRenameWithSorter
randomly fails, e.g. https://download.eclipse.org/eclipse/downloads/drops4/I20230810-1800/testresults/html/org.eclipse.jface.tests_ep429I-unit-macM1-java17_macosx.cocoa.aarch64_17.htmlThe text was updated successfully, but these errors were encountered: