action #96611

[qe-core][opensuse][sporadic] test fails in tomcat

Added by dimstar over 1 year ago. Updated about 1 year ago.

Bugs in existing tests
Target version:
Start date:
Due date:
% Done:


Estimated time:



openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-tomcat@64bit fails in

Test suite description

Install and test tomcat on Tumbleweed.


Fails since (at least) Build 20210804

Expected result

Last good: 20210803 (or more recent)

Further details

Check the history in this scenario: latest

Related issues

Related to openQA Tests - action #99417: [qe-core]test fails sporadically in tomcatResolved2021-09-28


#1 Updated by maritawerner over 1 year ago

  • Subject changed from test fails in tomcat to [qe-core] test fails in tomcat

#2 Updated by tjyrinki_suse over 1 year ago

  • Subject changed from [qe-core] test fails in tomcat to [qe-core][opensuse][sporadic] test fails in tomcat
  • Description updated (diff)
  • Status changed from New to Workable
  • Start date deleted (2021-08-05)

#3 Updated by zluo over 1 year ago

  • Status changed from Workable to In Progress
  • Assignee set to zluo
  • Target version set to QE-Core: Ready

take over and check this issue.

#5 Updated by zluo over 1 year ago

over 60 test runs on O3 and found following sporadic performance issue: (often)


#6 Updated by zluo over 1 year ago

except network issue on remote worker it looks goods for over 200 test runs:

So prepare PR with following changes:

diff --git a/lib/Tomcat/ b/lib/Tomcat/
index 96ab58c9f..a1b0469dc 100644
--- a/lib/Tomcat/
+++ b/lib/Tomcat/
@@ -262,13 +262,14 @@ sub form() {
     for (1 .. 2) { send_key('ret'); }

-    if (check_screen('tomcat-click-save-login', 10)) {
+    if (check_screen('tomcat-click-save-login', 60)) {
         assert_and_click('tomcat-click-save-login', TIMEOUT);

+    wait_still_screen;
     assert_screen('tomcat-form-example-result', TIMEOUT);

#9 Updated by zluo over 1 year ago

  • Related to action #99417: [qe-core]test fails sporadically in tomcat added

#10 Updated by zluo over 1 year ago

recently test run looks good, but wait for some more test run to be sure that this sporadic issue got fixed really.

#11 Updated by zluo over 1 year ago

looks like we have also sporadic issue on OSD:

On my local worker looks good, same build for tomcat.

#12 Updated by zluo over 1 year ago looks good with another worker.

#13 Updated by zluo over 1 year ago

what I found is that test failed at different stages of needle match 'tomcat-servlet-fallback' and other place like 'tomcat-snake-example-loaded':


#14 Updated by zluo over 1 year ago

the problem is that firefox_open_url doesn't work from time to time, this is clearly a performance issue.


# access the tomcat servlets examples page
    if ($mod_jk) {
    } else {
    send_key_until_needlematch('tomcat-servlet-examples-page', 'ret');

    # Navigate with keyboard to each example and test it
    for my $i (0 .. $#servlet_examples) {
        Tomcat::Utils->browse_with_keyboard('tomcat-servlet-fallback', $servlet_examples[$i][0], $servlet_examples[$i][1]);


sub firefox_open_url {
    my ($self, $url, $do_not_check_loaded_url) = @_;
    my $counter = 1;
    while (1) {
        # make sure firefox window is focused
        assert_and_click 'firefox_titlebar' if check_screen('firefox_titlebar', 2);
        wait_still_screen 1, 2;
        send_key 'alt-d';
        send_key 'delete';
        send_key 'alt-d';
        send_key 'delete';
        last if check_screen('firefox-empty-bar', 3);
        if ($counter++ > 5) {
            assert_screen('firefox-empty-bar', 0);
            last;    # in case it worked
    enter_cmd_slow "$url";
    wait_still_screen 2, 4;
    # this is because of adobe flash, screensaver will activate sooner than the page
    unless ($do_not_check_loaded_url) {
        assert_screen 'firefox-url-loaded', 300;

#18 Updated by openqa_review over 1 year ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: tomcat

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

#19 Updated by zluo about 1 year ago

  • Status changed from In Progress to Resolved

this issue doesn't happen for Tumbleweed anymore. No needle issue and performance looks better. Only one network issue can be seen, but it has nothing to do with the failure of tomcat. Since we have a open ticket which still has problem wit sles 15, I close it as resolved for now:

Also available in: Atom PDF