https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842016-11-08T22:48:08ZopenSUSE Project Management ToolopenQA Project - action #13242: WDYT: For every job that does not have a label or bugref, retrigger some times to see if it's sporadic. Like rescheduling on incomplete but on failedhttps://progress.opensuse.org/issues/13242?journal_id=311982016-11-08T22:48:08Zokurzokurz@suse.com
<ul><li><strong>Project</strong> changed from <i>openQA Tests</i> to <i>openQA Project</i></li></ul> openQA Project - action #13242: WDYT: For every job that does not have a label or bugref, retrigger some times to see if it's sporadic. Like rescheduling on incomplete but on failedhttps://progress.opensuse.org/issues/13242?journal_id=312862016-11-09T10:12:10Zcoolocoolo@suse.com
<ul></ul><p>the main problem with the automatic retriggering was (and will be) about the reporting - you hardly know if a running job is running for the first time or not and why it was restarted. Of course you'll see in the job if looking at it - but if you have 80 running jobs and 300 scheduled, you'll hardly notice.</p>
<p>The jobs I retrigger the most are actually the ones that <em>are</em> labeled ;(</p>
openQA Project - action #13242: WDYT: For every job that does not have a label or bugref, retrigger some times to see if it's sporadic. Like rescheduling on incomplete but on failedhttps://progress.opensuse.org/issues/13242?journal_id=363602017-01-17T14:57:36Zszarate
<ul><li><strong>Follows</strong> <i><a class="issue tracker-6 status-3 priority-4 priority-default closed child parent" href="/issues/14972">coordination #14972</a>: [tools][epic] Improvements on backend to improve better handling of stalls</i> added</li></ul> openQA Project - action #13242: WDYT: For every job that does not have a label or bugref, retrigger some times to see if it's sporadic. Like rescheduling on incomplete but on failedhttps://progress.opensuse.org/issues/13242?journal_id=364102017-01-17T15:59:53Zokurzokurz@suse.com
<ul><li><strong>Category</strong> set to <i>Feature requests</i></li></ul> openQA Project - action #13242: WDYT: For every job that does not have a label or bugref, retrigger some times to see if it's sporadic. Like rescheduling on incomplete but on failedhttps://progress.opensuse.org/issues/13242?journal_id=720762017-11-18T08:46:58Zcoolocoolo@suse.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li><li><strong>Target version</strong> set to <i>future</i></li></ul><p>What we'd need is a complete new handling of jobs including groups of them and such. Everything else requires external triggering/monitoring. 90% reject for me</p>
openQA Project - action #13242: WDYT: For every job that does not have a label or bugref, retrigger some times to see if it's sporadic. Like rescheduling on incomplete but on failedhttps://progress.opensuse.org/issues/13242?journal_id=1299672018-06-15T19:08:58Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> changed from <i>future</i> to <i>future</i></li></ul> openQA Project - action #13242: WDYT: For every job that does not have a label or bugref, retrigger some times to see if it's sporadic. Like rescheduling on incomplete but on failedhttps://progress.opensuse.org/issues/13242?journal_id=1423552018-08-14T13:15:18Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-6 status-3 priority-4 priority-default closed parent" href="/issues/39719">coordination #39719</a>: [saga][epic] Detection of "known failures" for stable tests, easy test results review and easy tracking of known issues</i> added</li></ul> openQA Project - action #13242: WDYT: For every job that does not have a label or bugref, retrigger some times to see if it's sporadic. Like rescheduling on incomplete but on failedhttps://progress.opensuse.org/issues/13242?journal_id=2716522020-01-15T14:54:56Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-6 status-1 priority-3 priority-lowest child" href="/issues/9966">coordination #9966</a>: [epic] Be more robust about spurious errors</i> added</li></ul> openQA Project - action #13242: WDYT: For every job that does not have a label or bugref, retrigger some times to see if it's sporadic. Like rescheduling on incomplete but on failedhttps://progress.opensuse.org/issues/13242?journal_id=2716582020-01-15T14:56:53Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Rejected</i></li><li><strong>Assignee</strong> set to <i>okurz</i></li></ul><p>The problem mentioned in <a class="issue tracker-4 status-6 priority-3 priority-lowest closed" title="action: WDYT: For every job that does not have a label or bugref, retrigger some times to see if it's spo... (Rejected)" href="https://progress.opensuse.org/issues/13242#note-2">#13242#note-2</a> is meanwhile fixed by the definition of a "scenario" and its history. The rest is for <a class="issue tracker-6 status-1 priority-3 priority-lowest child" title="coordination: [epic] Be more robust about spurious errors (New)" href="https://progress.opensuse.org/issues/9966">#9966</a> where I added the proposal of this ticket.</p>