action #101957
Updated by JERiveraMoya about 3 years ago
Test fails here https://openqa.suse.de/tests/7605134#step/skip_install_addons/1 even with timeout 90s, which means 180s (because internally we do a sleep of 1 second in one function and another sleep of 1 second in another one, which we still didn't tackle) We could potentially miss some bugs when more than 30 seconds is not acceptable for the screen to react. We should consider revert to lower timeout (check history what is the most proper one, although ideally 20 seconds by bug report but we want to have some margin) and provide extensive verification runs specially for the jobs with handle module selection or user creation, etc, where we need to wait more. For the failing test, here https://openqa.suse.de/tests/7605134#step/select_nonconflicting_modules/1 we could specifically wait more time, 150 120 seconds (which in reality is 300s). 240s).