https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842022-11-23T09:17:20ZopenSUSE Project Management ToolopenQA Tests - action #120834: [qe-core] tomcat: login to example app failshttps://progress.opensuse.org/issues/120834?journal_id=5772132022-11-23T09:17:20Zmaritawernermawerner@suse.com
<ul><li><strong>Subject</strong> changed from <i>tomcat: login to example app fails</i> to <i>[qe-core] tomcat: login to example app fails</i></li></ul> openQA Tests - action #120834: [qe-core] tomcat: login to example app failshttps://progress.opensuse.org/issues/120834?journal_id=5786142022-11-28T11:13:16Zdimstardimstar@opensuse.org
<ul></ul><p><a href="https://openqa.opensuse.org/tests/2910344#next_previous" class="external">https://openqa.opensuse.org/tests/2910344#next_previous</a></p>
<p>In the last week, the test had about a 50% success rate</p>
openQA Tests - action #120834: [qe-core] tomcat: login to example app failshttps://progress.opensuse.org/issues/120834?journal_id=5876862022-12-24T00:39:14Zopenqa_reviewopenqa-review@suse.de
<ul></ul><p>This is an autogenerated message for openQA integration by the openqa_review script:</p>
<p>This bug is still referenced in a failing openQA test: tomcat<br>
<a href="https://openqa.opensuse.org/tests/2974521#step/tomcat/1" class="external">https://openqa.opensuse.org/tests/2974521#step/tomcat/1</a></p>
<p>To prevent further reminder comments one of the following options should be followed:</p>
<ol>
<li>The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted</li>
<li>The openQA job group is moved to "Released" or "EOL" (End-of-Life)</li>
<li>The bugref in the openQA scenario is removed or replaced, e.g. <code>label:wontfix:boo1234</code></li>
</ol>
<p>Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.</p>
openQA Tests - action #120834: [qe-core] tomcat: login to example app failshttps://progress.opensuse.org/issues/120834?journal_id=5923932023-01-11T13:58:42Zdimstardimstar@opensuse.org
<ul></ul><p>Out of the last 10 runs, 50% failed, 50% succeeded</p>
openQA Tests - action #120834: [qe-core] tomcat: login to example app failshttps://progress.opensuse.org/issues/120834?journal_id=5928882023-01-12T11:51:53Zzluo
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Assignee</strong> set to <i>zluo</i></li><li><strong>Start date</strong> deleted (<del><i>2022-11-22</i></del>)</li></ul><p>let me check this issue.</p>
openQA Tests - action #120834: [qe-core] tomcat: login to example app failshttps://progress.opensuse.org/issues/120834?journal_id=5929512023-01-12T14:52:50Zzluo
<ul></ul><p><a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/16220" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/16220</a></p>
openQA Tests - action #120834: [qe-core] tomcat: login to example app failshttps://progress.opensuse.org/issues/120834?journal_id=5930172023-01-12T15:52:37Zzluo
<ul></ul><p>the issue with check tomcat status can be resolved as above WIP PR.</p>
<p>but I cannot understand how login works in tomcat:</p>
<p>JspTest.pm</p>
<pre><code class="xml syntaxhl" data-language="xml">...
sub form() {
assert_screen('tomcat-form-example', TIMEOUT);
send_key('tab');
send_key('down');
for (1 .. 2) { send_key('ret'); }
if (check_screen('tomcat-click-save-login', 60)) {
assert_and_click('tomcat-click-save-login', timeout => TIMEOUT);
}
send_key('tab');
type_string('tomcat');
send_key('ret');
wait_still_screen;
assert_screen('tomcat-form-example-result', TIMEOUT);
}
...
</code></pre> openQA Tests - action #120834: [qe-core] tomcat: login to example app failshttps://progress.opensuse.org/issues/120834?journal_id=5932992023-01-13T10:17:48Zzluo
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Workable</i></li><li><strong>Assignee</strong> deleted (<del><i>zluo</i></del>)</li></ul><p>since this is more likely a performance issue and we considered already to re-write the tomcat module, I will stop to work on it for now.#</p>
openQA Tests - action #120834: [qe-core] tomcat: login to example app failshttps://progress.opensuse.org/issues/120834?journal_id=5974962023-01-28T02:09:38Zopenqa_reviewopenqa-review@suse.de
<ul></ul><p>This is an autogenerated message for openQA integration by the openqa_review script:</p>
<p>This bug is still referenced in a failing openQA test: tomcat<br>
<a href="https://openqa.opensuse.org/tests/3076658#step/tomcat/1" class="external">https://openqa.opensuse.org/tests/3076658#step/tomcat/1</a></p>
<p>To prevent further reminder comments one of the following options should be followed:</p>
<ol>
<li>The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted</li>
<li>The openQA job group is moved to "Released" or "EOL" (End-of-Life)</li>
<li>The bugref in the openQA scenario is removed or replaced, e.g. <code>label:wontfix:boo1234</code></li>
</ol>
<p>Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.</p>
openQA Tests - action #120834: [qe-core] tomcat: login to example app failshttps://progress.opensuse.org/issues/120834?journal_id=6040132023-02-20T08:03:25Zzluo
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>Resolved</i></li><li><strong>Assignee</strong> set to <i>zluo</i></li></ul><p>test module tomcat has been changed and it looks good:<br>
<a href="https://openqa.opensuse.org/tests/3129521#next_previous" class="external">https://openqa.opensuse.org/tests/3129521#next_previous</a></p>