https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842018-08-01T10:02:07ZopenSUSE Project Management ToolopenQA Tests - action #39011: [functional] Low performance on openqa production serverhttps://progress.opensuse.org/issues/39011?journal_id=1396312018-08-01T10:02:07Zzluo
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/139631/diff?detail_id=140747">diff</a>)</li></ul> openQA Tests - action #39011: [functional] Low performance on openqa production serverhttps://progress.opensuse.org/issues/39011?journal_id=1404502018-08-06T13:42:49Zokurzokurz@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/37306">action #37306</a>: [opensuse][functional][u][sporadic] test fails in gimp - send_key doesn't work</i> added</li></ul> openQA Tests - action #39011: [functional] Low performance on openqa production serverhttps://progress.opensuse.org/issues/39011?journal_id=1404562018-08-06T13:42:55Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-6 priority-4 priority-default closed" href="/issues/37558">action #37558</a>: [opensuse][functional][u] test fails in systemsettings5 - send_key issue for closing application</i> added</li></ul> openQA Tests - action #39011: [functional] Low performance on openqa production serverhttps://progress.opensuse.org/issues/39011?journal_id=1404622018-08-06T13:43:01Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-6 priority-3 priority-lowest closed" href="/issues/38270">action #38270</a>: [functional][y][sporadic][aarch64] test fails in yast2_i - missing keys while searching for a package name</i> added</li></ul> openQA Tests - action #39011: [functional] Low performance on openqa production serverhttps://progress.opensuse.org/issues/39011?journal_id=1404682018-08-06T13:43:07Zokurzokurz@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/37354">action #37354</a>: [opensuse][functional][u][sporadic][medium] test fails in desktop_runner is unstable</i> added</li></ul> openQA Tests - action #39011: [functional] Low performance on openqa production serverhttps://progress.opensuse.org/issues/39011?journal_id=1404742018-08-06T13:46:11Zokurzokurz@suse.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/140474/diff?detail_id=141482">diff</a>)</li><li><strong>Category</strong> set to <i>Bugs in existing tests</i></li><li><strong>Target version</strong> set to <i>future</i></li></ul><p>hi, in redmine it's better to reference other tickets with just <code>#<id></code> so that we can see a preview and also the reference is striked through if already closed. Also some of the referenced issues are IMHO not pointing to low performance on specific workers but actually real issues which we needed to fix specifically as well as the limits of running single core VMs with 1GB of RAM or hardly more. What we can do though is to bump the memory we supply to the VMs as well as try to experiment with setting at least 2 cores by default.</p>
<p>Let's keep this ticket open for now and reference other related issues to see commonalities first before going further.</p>
openQA Tests - action #39011: [functional] Low performance on openqa production serverhttps://progress.opensuse.org/issues/39011?journal_id=1404772018-08-06T13:46:24Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>Low performance on openqa production server</i> to <i>[functional] Low performance on openqa production server</i></li></ul> openQA Tests - action #39011: [functional] Low performance on openqa production serverhttps://progress.opensuse.org/issues/39011?journal_id=1406902018-08-07T06:33:42Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-5 priority-high3 closed behind-schedule" href="/issues/39059">action #39059</a>: [sle][functional][y] detect "openSUSE sucks bug" about btrfs balance and record_soft_fail (was: yast2_gui tests modules as application could not start up)</i> added</li></ul> openQA Tests - action #39011: [functional] Low performance on openqa production serverhttps://progress.opensuse.org/issues/39011?journal_id=1406962018-08-07T06:34:36Zokurzokurz@suse.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/140696/diff?detail_id=141740">diff</a>)</li></ul> openQA Tests - action #39011: [functional] Low performance on openqa production serverhttps://progress.opensuse.org/issues/39011?journal_id=1407352018-08-07T07:44:42Zokurzokurz@suse.com
<ul></ul><p>Sorry, after reviewing the current test failures I do not buy into the argument of "low performance on production server". <a class="issue tracker-4 status-3 priority-5 priority-high3 closed behind-schedule" title="action: [sle][functional][y] detect "openSUSE sucks bug" about btrfs balance and record_soft_fail (was: y... (Resolved)" href="https://progress.opensuse.org/issues/39059">#39059</a> gives more details. As riafarov also investigated in jobs we more likely have a problem still/again with <a href="https://bugzilla.suse.com/show_bug.cgi?id=1063638" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1063638</a> . If there is anything else in specific cases then we should handle such as specific ones. Mentioning seemingly related job failures here should be beneficial nevertheless.</p>
openQA Tests - action #39011: [functional] Low performance on openqa production serverhttps://progress.opensuse.org/issues/39011?journal_id=1432192018-08-16T15:08:16Zzluo
<ul></ul><p>As we talked offline about this. I would like to see a plan to check worker monitoring (configurations and test results etc). </p>
openQA Tests - action #39011: [functional] Low performance on openqa production serverhttps://progress.opensuse.org/issues/39011?journal_id=1437352018-08-18T19:47:34Zokurzokurz@suse.com
<ul></ul><p>yes, that would be <a class="issue tracker-4 status-3 priority-4 priority-default closed parent" title="action: [devops][tools] monitoring of openqa worker instances (Resolved)" href="https://progress.opensuse.org/issues/18164">#18164</a></p>
openQA Tests - action #39011: [functional] Low performance on openqa production serverhttps://progress.opensuse.org/issues/39011?journal_id=1558702018-10-11T20:15:04Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li><li><strong>Assignee</strong> set to <i>okurz</i></li></ul><p>I think by now we have found a better understanding and do not need this very generic ticket anymore in favor of the mentioned more specific ones.</p>