Project

General

Profile

Actions

action #63244

closed

Ensure apache timeouts are higher than openQA internal ones (was: Latest version of openQA webui dashboard can not display big test result)

Added by tonyyuan over 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2020-02-07
Due date:
% Done:

0%

Estimated time:

Description

I used qa_automation/qa_run to schedule bash,bzip2,openssl,php5 testsuites. The job completed successfully but I could not open the test result from dashboard web page. I think it's because that php5 has more than 10000 test cases.

openQA version:
openQA-4.6.1581058621.9523164cd-2260.1.noarc

in the /var/log/openqa

[2020-02-07T19:24:15.0620 CST] [debug] [pid:8897] Reading information from {"_source":"parser","display_title":"PHPTEST-tests-lang-foreachLoopObjects.001","num":12484,"result":"ok","text":"php5-1_php5-12484.txt","title":"PHPTEST-tests-lang-foreachLoopObjects.001"}
[2020-02-07T19:24:15.0620 CST] [debug] [pid:8897] Reading information from {"_source":"parser","display_title":"PHPTEST-tests-lang-foreachLoopObjects.002","num":12485,"result":"ok","text":"php5-1_php5-12485.txt","title":"PHPTEST-tests-lang-foreachLoopObjects.002"}
[2020-02-07T19:24:15.0620 CST] [debug] [pid:8897] Reading information from {"_source":"parser","display_title":"PHPTEST-tests-lang-foreachLoopObjects.003","num":12486,"result":"ok","text":"php5-1_php5-12486.txt","title":"PHPTEST-tests-lang-foreachLoopObjects.003"}
[2020-02-07T19:24:15.0620 CST] [debug] [pid:8897] Reading information from {"_source":"parser","display_title":"PHPTEST-tests-lang-foreachLoopObjects.004","num":12487,"result":"ok","text":"php5-1_php5-12487.txt","title":"PHPTEST-tests-lang-foreachLoopObjects.004"}
[2020-02-07T19:24:15.0620 CST] [debug] [pid:8897] Reading information from {"_source":"parser","display_title":"PHPTEST-tests-lang-foreachLoopObjects.005","num":12488,"result":"ok","text":"php5-1_php5-12488.txt","title":"PHPTEST-tests-lang-foreachLoopObjects.005"}
[2020-02-07T19:24:15.0620 CST] [debug] [pid:8897] Reading information from {"_source":"parser","display_title":"PHPTEST-tests-lang-foreachLoopObjects.006","num":12489,"result":"ok","text":"php5-1_php5-12489.txt","title":"PHPTEST-tests-lang-foreachLoopObjects.006"}
[2020-02-07T19:24:15.0620 CST] [debug] [pid:8897] Reading information from {"_source":"parser","display_title":"PHPTEST-tests-lang-foreach_with_object_001","num":12490,"result":"ok","text":"php5-1_php5-12490.txt","title":"PHPTEST-tests-lang-foreach_with_object_001"}
[2020-02-07T19:24:15.0620 CST] [debug] [pid:8897] Reading information from {"_source":"parser","display_title":"PHPTEST-tests-lang-foreach_with_references_001","num":12491,"result":"ok","text":"php5-1_php5-12491.txt","title":"PHPTEST-tests-lang-foreach_with_references_001"}
[2020-02-07T19:24:15.0621 CST] [debug] [pid:8897] Reading information from {"_source":"parser","display_title":"PHPTEST-tests-lang-func_get_arg.001","num":12492,"result":"ok","text":"php5-1_php5-12492.txt","title":"PHPTEST-tests-lang-func_get_arg.001"}
[2020-02-07T19:24:15.0621 CST] [debug] [pid:8897] Reading information from {"_source":"p
....

[2020-02-07T19:24:15.0661 CST] [debug] [79574130] Rendering template "test/result.html.ep"
[2020-02-07T19:24:15.0666 CST] [debug] [79574130] Rendering template "layouts/info.html.ep"
[2020-02-07T19:24:15.0668 CST] [debug] [79574130] Rendering template "test/infopanel.html.ep"
[2020-02-07T19:24:15.0682 CST] [debug] [79574130] Rendering template "test/details.html.ep"
[2020-02-07T19:24:15.0683 CST] [debug] [79574130] Rendering template "test/module_table.html.ep"
[2020-02-07T19:24:15.0713 CST] [debug] [79574130] Rendering template "branding/openSUSE/external_reporting.html.ep"
[2020-02-07T19:24:15.0724 CST] [debug] [79574130] Rendering cached template "branding/openSUSE/external_reporting.html.ep"
[2020-02-07T19:24:15.0733 CST] [debug] [79574130] Rendering cached template "branding/openSUSE/external_reporting.html.ep"
[2020-02-07T19:24:15.0741 CST] [debug] [79574130] Rendering cached template "branding/openSUSE/external_reporting.html.ep"
[2020-02-07T19:24:15.0749 CST] [debug] [79574130] Rendering cached template "branding/openSUSE/external_reporting.html.ep"
[2020-02-07T19:24:15.0757 CST] [debug] [79574130] Rendering cached template "branding/openSUSE/external_reporting.html.ep"
[2020-02-07T19:24:15.0765 CST] [debug] [79574130] Rendering cached template "branding/openSUSE/external_reporting.html.ep"
[2020-02-07T19:24:15.0773 CST] [debug] [79574130] Rendering cached template "branding/openSUSE/external_reporting.html.ep"
[2020-02-07T19:24:15.0781 CST] [debug] [79574130] Rendering cached template "branding/openSUSE/external_reporting.html.ep"
[2020-02-07T19:24:15.0789 CST] [debug] [79574130] Rendering cached template "branding/openSUSE/external_reporting.html.ep"
[2020-02-07T19:24:15.0797 CST] [debug] [79574130] Rendering cached template "branding/openSUSE/external_reporting.html.ep"
[2020-02-07T19:24:15.0805 CST] [debug] [79574130] Rendering cached template "branding/openSUSE/external_reporting.html.ep"
[2020-02-07T19:24:15.0812 CST] [debug] [79574130] Rendering cached template "branding/openSUSE/external_reporting.html.ep"
[2020-02-07T19:24:15.0820 CST] [debug] [79574130] Rendering cached template "branding/openSUSE/external_reporting.html.ep"
[2020-02-07T19:24:15.0828 CST] [debug] [79574130] Rendering cached template "branding/openSUSE/external_reporting.html.ep"

Related issues 1 (0 open1 closed)

Is duplicate of openQA Project - action #34855: [kernel] "ltp_openposix" test results are taking too long to load -> timeoutResolved2018-04-12

Actions
Actions #1

Updated by tonyyuan over 4 years ago

here is the example http://10.67.17.201/tests/432.
http://10.67.17.201/tests/420
I could opened it and saw the result 3 weeks ago before I upgraded. So I think this issue a regression.

Actions #2

Updated by okurz over 4 years ago

  • Is duplicate of action #34855: [kernel] "ltp_openposix" test results are taking too long to load -> timeout added
Actions #3

Updated by okurz over 4 years ago

  • Subject changed from Latested version Openqa-webui dashborad can not display big test result to Latest version of openQA webui dashboard can not display big test result
  • Category set to Feature requests
  • Status changed from New to Rejected
  • Assignee set to okurz

That too many results cause incomplete loading is known, see #34855. I doubt it's a regression due to recent changes in openQA, maybe even more test results are in the job or currently the openQA instance can not serve as fast as expected. It might be possible to load the results during "more quiet" times.

As a workaround it is suggested to change tests to not provide that many individual test result steps.

Actions #4

Updated by mkittler over 4 years ago

I've wrote this before I saw the comment of @okurz:

What means "can not display"? If you run into a timeout you can simply increase the timeout (on Mojolicious level and within your reverse proxy if you're using one).

I don't think we have a (significant) performance regression. The performance was always slow if you have too many external result because the way we store them simply doesn't scale. That's something we generally need to improve. Note that the performance also highly depends on your file system performance and is e.g. influenced by caching.

Actions #5

Updated by tonyyuan about 4 years ago

I think I found the root cause. I saw the message below in /var/log/openqa.
...
[2020-02-10T14:36:07.0911 CST] [debug] [efc6a5b3] 200 OK (103.672585s, 0.010/s)

It indicates that it took around 103 seconds for openQA-webui to finish parsing, rendering.
Weheras the apache2 proxy waiting timeout defaults to 60s. That was why my browser couldn't load results page.
I added "ProxyTimeout 300" in /etc/apache2/vhosts.d/openqa-common.inc to raise it. Now I can open it.

Actions #6

Updated by okurz about 4 years ago

  • Subject changed from Latest version of openQA webui dashboard can not display big test result to Ensure apache timeouts are higher than openQA internal ones (was: Latest version of openQA webui dashboard can not display big test result)
  • Status changed from Rejected to Workable
  • Assignee deleted (okurz)

Cool that you found the solution. I think we can improve this also on the side of openQA accordingly then, e.g. have the apache config files that we deliver have a higher timeout than openQA internal ones.

Actions #7

Updated by ilausuch about 4 years ago

  • Status changed from Workable to In Progress
  • Assignee set to ilausuch
Actions #8

Updated by livdywan about 4 years ago

  • Description updated (diff)
Actions #9

Updated by ilausuch about 4 years ago

https://github.com/os-autoinst/openQA/pull/2964

I set the timeout to 300s that is the tested one.

Actions #10

Updated by livdywan about 4 years ago

  • Target version set to Current Sprint

PR is done and approved, pending on (flaky) test failures.

Actions #11

Updated by okurz about 4 years ago

I do not see anything flaky about the test failures.

Actions #12

Updated by okurz about 4 years ago

  • Status changed from In Progress to Resolved

PR merged but I don't think we can easily reproduce the problem. I am confident this is enough for now. To be effective on osd we need to wait a week for the next automatic deploy though

Actions

Also available in: Atom PDF