https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842019-05-21T08:45:14ZopenSUSE Project Management ToolopenQA Project - action #51716: No scheduling error generated for faulty PARALLEL_WITH confighttps://progress.opensuse.org/issues/51716?journal_id=2134642019-05-21T08:45:14Zasmorodskyi
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/213464/diff?detail_id=211016">diff</a>)</li></ul> openQA Project - action #51716: No scheduling error generated for faulty PARALLEL_WITH confighttps://progress.opensuse.org/issues/51716?journal_id=2134672019-05-21T08:46:19Zasmorodskyi
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/213467/diff?detail_id=211019">diff</a>)</li></ul> openQA Project - action #51716: No scheduling error generated for faulty PARALLEL_WITH confighttps://progress.opensuse.org/issues/51716?journal_id=2221972019-06-20T15:16:15Zokurzokurz@suse.com
<ul><li><strong>Category</strong> set to <i>Regressions/Crashes</i></li></ul> openQA Project - action #51716: No scheduling error generated for faulty PARALLEL_WITH confighttps://progress.opensuse.org/issues/51716?journal_id=2906102020-04-03T12:06:14Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>No error on scheduling faulty MM config</i> to <i>Make scheduling errors more accessible. There is no error on scheduling faulty MM config</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/290610/diff?detail_id=287439">diff</a>)</li><li><strong>Category</strong> changed from <i>Regressions/Crashes</i> to <i>Feature requests</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Workable</i></li><li><strong>Target version</strong> set to <i>future</i></li></ul><p>Merged in content from <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: Make scheduling errors more accessible (Resolved)" href="https://progress.opensuse.org/issues/65142">#65142</a></p>
openQA Project - action #51716: No scheduling error generated for faulty PARALLEL_WITH confighttps://progress.opensuse.org/issues/51716?journal_id=2906162020-04-03T12:06:28Zokurzokurz@suse.com
<ul><li><strong>Has duplicate</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed" href="/issues/65142">action #65142</a>: Make scheduling errors more accessible</i> added</li></ul> openQA Project - action #51716: No scheduling error generated for faulty PARALLEL_WITH confighttps://progress.opensuse.org/issues/51716?journal_id=2985672020-05-07T09:34:25Zmkittlermarius.kittler@suse.com
<ul><li><strong>Has duplicate</strong> deleted (<i><a class="issue tracker-4 status-3 priority-4 priority-default closed" href="/issues/65142">action #65142</a>: Make scheduling errors more accessible</i>)</li></ul> openQA Project - action #51716: No scheduling error generated for faulty PARALLEL_WITH confighttps://progress.opensuse.org/issues/51716?journal_id=2985702020-05-07T09:34:34Zmkittlermarius.kittler@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed" href="/issues/65142">action #65142</a>: Make scheduling errors more accessible</i> added</li></ul> openQA Project - action #51716: No scheduling error generated for faulty PARALLEL_WITH confighttps://progress.opensuse.org/issues/51716?journal_id=2985792020-05-07T09:53:20Zmkittlermarius.kittler@suse.com
<ul><li><strong>Subject</strong> changed from <i>Make scheduling errors more accessible. There is no error on scheduling faulty MM config</i> to <i>No scheduling error generated for faulty PARALLEL_WITH config</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/298579/diff?detail_id=295534">diff</a>)</li></ul><p>I moved the information copied over from <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: Make scheduling errors more accessible (Resolved)" href="https://progress.opensuse.org/issues/65142">#65142</a> out again because these are actually different issues. I keep the <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: Make scheduling errors more accessible (Resolved)" href="https://progress.opensuse.org/issues/65142">#65142</a> as related issue because both are about scheduling errors.</p>
<p>About the issue itself: I'm wondering whether it makes sense to assume <code>PARALLEL_WITH</code> dependencies can be cyclic at all. I mean, these jobs are supposed to run together at the same time making a "job cluster" in any case: If job <code>A</code> is supposed to run in parallel with job <code>B</code> that means implicitly that job <code>B</code> is supposed to run in parallel with <code>A</code>. I see no problem in specifying that explicitly. (And by the way, if <code>B</code> is additionally supposed to run in parallel with <code>C</code> that also implies <code>A</code> is supposed to run in parallel with <code>C</code>.)</p>