Christian Rösch

Not yet worked on this issue. These comments were generated automatically by importing the issue. So is it the exact same problem? Tests block without exception?

Could you provide some thread dumps?

Hello @krish0307 do you use the `@GUITestRunner`? Do you run your tests with JUnit?

__Hint__ (thanks to @lbalazscs) Recently I debugged a predictability issue in assertj-swing, maybe it helps you with the tests. I had some strange behavior that appeared only in some Linux...

__The list of (sometimes) failing tests__ ``` AbstractButtonDriver_click_Test.should_Click_Disabled_Button expected: but was: AbstractButtonDriver_select_Test.should_Select_Button expected: but was: AbstractButtonDriver_unselect_Test.should_Unselect_Button expected: but was: AbstractContainerFixture_dialog_Test.should_Find_Visible_Dialog_By_Name_That_Needs_A_Couple_Of_Seconds_To_Appear:67 » WaitTimedOut AbstractContainerFixture_fileChooser_Test.should_Find_Visible_JFileChooser_By_Matcher:115 » WaitTimedOut AbstractContainerFixture_fileChooser_Test.should_Find_Visible_JFileChooser_By_Type:85 » WaitTimedOut AbstractContainerFixture_optionPane_Test.should_Find_Visible_JOptionPane_By_Type_With_Timeout:56 »...

Thanks for opening the issue. I've a slightly different solution in mind. How about using `Settings` to declare a timeout? Would that help you, too?

Could you provide a basic code snippet where this would help you? I would like to have an approach that e.g. WindowFinder uses: `.withTimeout(10000)`..

No feedback :-/

Unfortunately no response yet. The documented solution works for me but I neither use gradle nor Windows 10. What is the error in your case?

Did you try to make a screenshot of the failure? On Linux there is sometimes a difference of the UI features available.. e.g. the title bar could be missing. So...