https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842016-05-24T14:15:46ZopenSUSE Project Management ToolopenQA Tests - action #12110: gnome_control_center: short timeout on details caused test to failhttps://progress.opensuse.org/issues/12110?journal_id=236542016-05-24T14:15:46Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>gnome_control_center: short timeout on details caued test to fail</i> to <i>gnome_control_center: short timeout on details caused test to fail</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/23654/diff?detail_id=24660">diff</a>)</li></ul><ol>
<li>sounds like a very good idea to me.</li>
</ol>
<p><code>git grep 'assert_screen.*, [0-9];'</code> yields still a whole lot of locations where we use assert_screen with a pretty low timeout, e.g. in x11 regression tests. We could set them all back to the default of 30 but I prefer to keep them and rather handle these failures accordingly. Interlinked to <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: Improved logging for debugging performance related issues (Resolved)" href="https://progress.opensuse.org/issues/12064">#12064</a></p>
openQA Tests - action #12110: gnome_control_center: short timeout on details caused test to failhttps://progress.opensuse.org/issues/12110?journal_id=236562016-05-24T14:16:08Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed" href="/issues/12064">action #12064</a>: Improved logging for debugging performance related issues</i> added</li></ul> openQA Tests - action #12110: gnome_control_center: short timeout on details caused test to failhttps://progress.opensuse.org/issues/12110?journal_id=236602016-05-24T14:18:31Zokurzokurz@suse.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/23660/diff?detail_id=24666">diff</a>)</li></ul> openQA Tests - action #12110: gnome_control_center: short timeout on details caused test to failhttps://progress.opensuse.org/issues/12110?journal_id=240562016-06-04T15:35:18Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul><p>idea: <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/1437" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/1437</a></p>
openQA Tests - action #12110: gnome_control_center: short timeout on details caused test to failhttps://progress.opensuse.org/issues/12110?journal_id=255542016-07-27T09:20:45Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li></ul><p>fixed with <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/1574" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/1574</a></p>
<p>The idea in <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/1437" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/1437</a> was deemed to be too complicated. The common understanding is: openQA is not really suitable for checking performance regressions by relying on hard timeouts. A better approach might be to read out the match times from the log files or add this data to some result files from which nice graphs could be rendered and such. For the issue at hand: Solved.</p>