-
Notifications
You must be signed in to change notification settings - Fork 23
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
Allow the post_fail_hook ip command to fail #165
Conversation
It may fail in case this IP is not actually set on the bridge. Also the ctrl-c needs to happen before, because if the grep ... tail -f -n0 nohup.out fails, it's not killed. Since ctrl-c shouldn't do any harm, I guess we can do it regardless of which test we are running. This ensures that the post_fail_hook can be completed.
ecca383
to
3e7addc
Compare
Ok, now the post_fail_hook suceeds. |
tail -F will wait for the ile to appear. It seems that the sleep 1 after the file appears is too slow and the first line [info] Listening at "http://127.0.0.1:9526" has already gone away when the grep starts.
Added another commit that improves the grepping of nohup.out, this fixes these sporadic failures: The content of the nohup.out is:
So everything worked, but it still ran into the timeout, that's why I realized that the |
It may fail in case this IP is not actually set on the bridge.
Also the ctrl-c needs to happen before, because if the
fails, it's not killed. Since ctrl-c shouldn't do any harm, I guess we can
do it regardless of which test we are running.
This ensures that the post_fail_hook can be completed.
Also this fixes sporadic failures in openqa_from_git: https://openqa.opensuse.org/tests/3946911#step/openqa_webui/36