https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842022-10-13T09:15:28ZopenSUSE Project Management ToolopenQA Project - action #118597: openqa-in-openqa test does not stop immediately on "Connect timeout", missing pipefail option? Job fails later size:Mhttps://progress.opensuse.org/issues/118597?journal_id=5629992022-10-13T09:15:28Zlivdywanliv.dywan@suse.com
<ul><li><strong>Subject</strong> changed from <i>openqa-in-openqa test does not stop immediately on "Connect timeout", missing pipefail option? Job fails later</i> to <i>openqa-in-openqa test does not stop immediately on "Connect timeout", missing pipefail option? Job fails later size:M</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Workable</i></li></ul> openQA Project - action #118597: openqa-in-openqa test does not stop immediately on "Connect timeout", missing pipefail option? Job fails later size:Mhttps://progress.opensuse.org/issues/118597?journal_id=5645892022-10-18T12:16:58Zmkittlermarius.kittler@suse.com
<ul><li><strong>Assignee</strong> set to <i>mkittler</i></li></ul> openQA Project - action #118597: openqa-in-openqa test does not stop immediately on "Connect timeout", missing pipefail option? Job fails later size:Mhttps://progress.opensuse.org/issues/118597?journal_id=5646072022-10-18T13:03:35Zmkittlermarius.kittler@suse.com
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>Feedback</i></li></ul><p>PR: <a href="https://github.com/os-autoinst/os-autoinst-distri-openQA/pull/102" class="external">https://github.com/os-autoinst/os-autoinst-distri-openQA/pull/102</a></p>
openQA Project - action #118597: openqa-in-openqa test does not stop immediately on "Connect timeout", missing pipefail option? Job fails later size:Mhttps://progress.opensuse.org/issues/118597?journal_id=5669832022-10-25T11:45:50Zmkittlermarius.kittler@suse.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>The PR has been merged. There has only been one failure since then but it had failed in a different module. I suppose we can resolve the PR nevertheless as I also did some local testing (see PR comment).</p>