https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842017-12-01T23:21:38ZopenSUSE Project Management ToolopenQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=762562017-12-01T23:21:38Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-6 priority-4 priority-default closed" href="/issues/19476">action #19476</a>: [migration]test fails in force_cron_run by assert_script_run failed</i> added</li></ul> openQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=762602017-12-01T23:22:01Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed" href="/issues/21798">action #21798</a>: [functional]test fails in force_cron_run, idle threshold to high</i> added</li></ul> openQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=762652017-12-01T23:22:16Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-6 priority-4 priority-default closed" href="/issues/23556">action #23556</a>: [sle][functional]test fails in force_cron_run because of missing file /usr/lib/cron/run-crons</i> added</li></ul> openQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=762692017-12-01T23:22:53Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed" href="/issues/28364">action #28364</a>: [sle][functional] remove reference to "btrfs cron jobs kills system responsiveness"-bug and workaround in console/force_cron_run</i> added</li></ul> openQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=762742017-12-01T23:23:04Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed behind-schedule" href="/issues/27597">action #27597</a>: [sle][functional] test fails in force_cron_run - Wrong bug ticket assigned</i> added</li></ul> openQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=762802017-12-01T23:23:51Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>soft fail in force_cron_run is too strict</i> to <i>[functional]soft fail in force_cron_run is too strict</i></li><li><strong>Due date</strong> set to <i>2018-01-16</i></li><li><strong>Target version</strong> set to <i>Milestone 13</i></li></ul> openQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=837702018-01-17T09:20:51Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> changed from <i>2018-01-16</i> to <i>2018-01-30</i></li></ul><p>mass-shift of tickets to next sprint due to training on sprint review day</p>
openQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=838242018-01-17T09:53:06Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> changed from <i>2018-01-30</i> to <i>2018-02-13</i></li></ul> openQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=891852018-02-07T10:05:56Zokurzokurz@suse.com
<ul><li><strong>Assignee</strong> set to <i>okurz</i></li></ul> openQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=891882018-02-07T10:06:34Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>[functional]soft fail in force_cron_run is too strict</i> to <i>[functional][bsc#1063638]soft fail in force_cron_run is too strict</i></li><li><strong>Due date</strong> changed from <i>2018-02-13</i> to <i>2018-05-15</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Blocked</i></li><li><strong>Target version</strong> changed from <i>Milestone 13</i> to <i>Milestone 15</i></li></ul><p>Now test tracks <a href="https://bugzilla.suse.com/show_bug.cgi?id=1063638" class="external">bsc#1063638</a>, will set ticket to blocked and review progress on bug later.</p>
openQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=916422018-02-16T20:05:38ZStefanBruensstefan.bruens@rwth-aachen.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-5 priority-high3 closed behind-schedule" href="/issues/31351">action #31351</a>: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)</i> added</li></ul> openQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=916482018-02-16T21:24:31ZStefanBruensstefan.bruens@rwth-aachen.de
<ul></ul><p>Currently settle_load reports any time above 30 seconds as a softfailure, which is too short IMHO:</p>
<ul>
<li>load average (first value) is a 1 minute sliding window average. Even for a completely idle system this value can be arbitrarily large for any time < 1 minute.</li>
<li>force_cron_run is executed immediately after boot, some large values (>>= 1) in the window are to be expected</li>
<li>starting top will likely contribute to the load (once), as processes waiting for disk I/O contribute to the load value.</li>
</ul>
<p>A timeout of 70 seconds (60 seconds window plus startup) is likely more appropriate.</p>
openQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=944262018-02-26T11:35:51Zokurzokurz@suse.com
<ul></ul><p>That sounds very reasonable. We should do that, switch to 70 seconds.</p>
openQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=1089552018-04-02T18:32:56Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> changed from <i>2018-05-15</i> to <i>2018-05-08</i></li></ul> openQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=1136172018-04-18T09:31:46Zmgriessmeiermgriessmeier@suse.com
<ul><li><strong>Subject</strong> changed from <i>[functional][bsc#1063638]soft fail in force_cron_run is too strict</i> to <i>[functional][bsc#1063638][u]soft fail in force_cron_run is too strict</i></li></ul> openQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=1157862018-04-25T14:39:42Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>[functional][bsc#1063638][u]soft fail in force_cron_run is too strict</i> to <i>[functional][bsc#1063638][u] soft fail in force_cron_run is too strict</i></li><li><strong>Status</strong> changed from <i>Blocked</i> to <i>Workable</i></li><li><strong>Assignee</strong> deleted (<del><i>okurz</i></del>)</li><li><strong>Target version</strong> changed from <i>Milestone 15</i> to <i>Milestone 16</i></li></ul><p>see comment <a class="issue tracker-4 status-3 priority-4 priority-default closed behind-schedule" title="action: [functional][bsc#1063638][u] soft fail in force_cron_run is too strict (Resolved)" href="https://progress.opensuse.org/issues/25554#note-12">#25554#note-12</a> and <a class="issue tracker-4 status-3 priority-4 priority-default closed behind-schedule" title="action: [functional][bsc#1063638][u] soft fail in force_cron_run is too strict (Resolved)" href="https://progress.opensuse.org/issues/25554#note-13">#25554#note-13</a></p>
openQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=1175012018-05-03T07:38:27Zzluo
<ul><li><strong>Assignee</strong> set to <i>zluo</i></li></ul><p>take over</p>
openQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=1175072018-05-03T07:58:14Zzluo
<ul></ul><p>reference test:</p>
<p><a href="http://openqa.suse.de/tests/1657020" class="external">http://openqa.suse.de/tests/1657020</a></p>
openQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=1175162018-05-03T08:10:10Zzluo
<ul></ul><p>I found that bsc#1063638 is not fixed yet.</p>
<pre><code>record_soft_failure 'bsc#1063638' if (time - $before) > (is_jeos() ? 180 : 30);
</code></pre> openQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=1175222018-05-03T08:44:26Zzluo
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>In Progress</i></li></ul> openQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=1179662018-05-07T08:11:58Zzluo
<ul></ul><p><a href="http://e13.suse.de/tests/2258" class="external">http://e13.suse.de/tests/2258</a></p>
<p>change:<br>
record_soft_failure 'bsc#1063638' if (time - $before) > (is_jeos() ? 180 : 70);</p>
openQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=1179782018-05-07T08:32:14Zzluo
<ul></ul><p>it looks good, no softfailed now.</p>
openQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=1179792018-05-07T08:34:42Zokurzokurz@suse.com
<ul></ul><p>Please collect more statistics on this, e.g. run at least 20 jobs</p>
openQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=1180272018-05-07T09:59:09Zzluo
<ul></ul><p>PR: <br>
<a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4904" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4904</a></p>
openQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=1181012018-05-07T15:18:39Zzluo
<ul></ul><p>my test runs show different test results: some got passed, some still softfailed.</p>
<p><a href="http://e13.suse.de/tests" class="external">http://e13.suse.de/tests</a></p>
openQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=1182852018-05-08T08:47:07Zmgriessmeiermgriessmeier@suse.com
<ul><li><strong>Due date</strong> changed from <i>2018-05-08</i> to <i>2018-05-22</i></li><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li></ul> openQA Tests - action #25554: [functional][bsc#1063638][u] soft fail in force_cron_run is too stricthttps://progress.opensuse.org/issues/25554?journal_id=1185102018-05-09T07:29:13Zzluo
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>test results on osd:</p>
<p><a href="https://openqa.suse.de/tests/1676524#step/force_cron_run/6" class="external">https://openqa.suse.de/tests/1676524#step/force_cron_run/6</a></p>