Workaround boot timeout issue for user_defined_snapshot.pm #5311
Conversation
- increase timeout for boot - see https://progress.opensuse.org/issues/35011 for details - verification run: http://e13.suse.de/tests/6015#step/user_defined_snapshot
|
Isn't it a sporadic issue? Then we should have more than one job for verification, right? |
|
can someone review this or reject this with comment, please? |
|
Actually I checked this for about 10 times, but if it is really need to run 40 or 50 times, that is not a problem. I think this is related to timeout. |
|
Can you please provide a link to the multiple test runs so that we can crosscheck the statistics? |
|
please see some test results: |
|
so 7 out of 40 failed - all those were triggered with your increased timeout included? |
|
@Soulofdestiny I re-triggered test runs: 5 failed from 50 test runs, failure is still too high. Any suggestions? |
|
I assume @dgutu-suse does not want to maintain the test module anymore so we should find a new maintainer. volunteers? |
|
@Zaoliang Also see my comment in https://progress.opensuse.org/issues/35011#note-16 . It seems the failures fail in shutdown not booting. Also I recommend to use the approach mentioned in https://progress.opensuse.org/projects/openqatests/wiki/#Statistical-investigation to define a custom "build" where it is easier to see statistics than looking into the history of a single test scenario. |
|
Is this still relevant? I don't see how it can help as we don't see grub which is one step before. |
|
@rwx788 no, since we have already handled shutdown/reboot issue. |
http://e13.suse.de/tests/6015#step/user_defined_snapshot