openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842024-03-18T10:06:13ZopenSUSE Project Management Tool
Redmine openQA Infrastructure - action #157453 (Rejected): [FIRING:1] host_up (qesapworker-prg5: host up ...https://progress.opensuse.org/issues/1574532024-03-18T10:06:13Zdheidlerdheidler@suse.com
<p><a href="https://stats.openqa-monitor.qa.suse.de/alerting/grafana/host_up_alert_qesapworker-prg5/view?orgId=1" class="external">https://stats.openqa-monitor.qa.suse.de/alerting/grafana/host_up_alert_qesapworker-prg5/view?orgId=1</a></p>
<p>The worker seemed to have hung up. No login prompt on serial tty.<br>
Rebooted via IPMI.<br>
Worker came up, but a systemd service failed:</p>
<pre><code># systemctl status openqa_nvme_format.service
× openqa_nvme_format.service - Setup NVMe before mounting it
Loaded: loaded (/etc/systemd/system/openqa_nvme_format.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2024-03-18 11:01:18 CET; 3min 30s ago
Process: 31734 ExecStart=/usr/local/bin/openqa-establish-nvme-setup (code=exited, status=1/FAILURE)
Main PID: 31734 (code=exited, status=1/FAILURE)
Mar 18 11:01:17 qesapworker-prg5 openqa-establish-nvme-setup[31739]: │ /boot/grub2/i386-pc
Mar 18 11:01:17 qesapworker-prg5 openqa-establish-nvme-setup[31739]: │ /.snapshots
Mar 18 11:01:17 qesapworker-prg5 openqa-establish-nvme-setup[31739]: │ /
Mar 18 11:01:17 qesapworker-prg5 openqa-establish-nvme-setup[31739]: └─sda3 8:3 0 1G 0 part [SWAP]
Mar 18 11:01:17 qesapworker-prg5 openqa-establish-nvme-setup[31734]: Creating RAID0 "/dev/md/openqa" on: /dev/disk/by-id/scsi-SDELL_PERC_H755_Adp_00e7176dba09d4532c00f9c13280e04e
Mar 18 11:01:17 qesapworker-prg5 openqa-establish-nvme-setup[31748]: mdadm: cannot open /dev/disk/by-id/scsi-SDELL_PERC_H755_Adp_00e7176dba09d4532c00f9c13280e04e: No such file or directory
Mar 18 11:01:17 qesapworker-prg5 openqa-establish-nvme-setup[31734]: Unable to create RAID, mdadm returned with non-zero code
Mar 18 11:01:18 qesapworker-prg5 systemd[1]: openqa_nvme_format.service: Main process exited, code=exited, status=1/FAILURE
Mar 18 11:01:18 qesapworker-prg5 systemd[1]: openqa_nvme_format.service: Failed with result 'exit-code'.
Mar 18 11:01:18 qesapworker-prg5 systemd[1]: Failed to start Setup NVMe before mounting it.
</code></pre>
<p>It seems like the NVMe disk is not found anymore. Maybe it died and the system subsequently freezed.</p>
openQA Tests - action #153766 (New): [core][sporadic] Handle wild agetty better in tests/network/...https://progress.opensuse.org/issues/1537662024-01-17T09:51:24Zdheidlerdheidler@suse.com
<p><a href="https://openqa.opensuse.org/tests/3874464" class="external">https://openqa.opensuse.org/tests/3874464</a><br>
<a href="https://github.com/os-autoinst/os-autoinst-distri-openQA/pull/159#issuecomment-1894506514" class="external">https://github.com/os-autoinst/os-autoinst-distri-openQA/pull/159#issuecomment-1894506514</a></p>
<p>This happens around 2 in 100 multi machine jobs so or 1 in 100 individual jobs.</p>
<p>A wild agetty appeared:</p>
<pre><code>[2024-01-16T11:45:41.007648-05:00] [debug] [pid:10982] <<< testapi::type_string(string="(echo qQf4r; bash -eox pipefail /tmp/scriptqQf4r.sh ; echo SCRIPT_FINISHEDqQf4r-\$?-) | tee /dev/ttyS0\n", max_interval=250,
wait_screen_change=0, wait_still_screen=0, timeout=30, similarity_level=47)
[2024-01-16T11:45:45.176979-05:00] [debug] [pid:10982] tests/network/setup_multimachine.pm:45 called mm_network::setup_static_mm_network -> lib/mm_network.pm:228 called mm_network::configure_static_dns -> lib/mm_
network.pm:130 called testapi::script_output
[2024-01-16T11:45:45.178288-05:00] [debug] [pid:10982] <<< testapi::wait_serial(regexp="SCRIPT_FINISHEDqQf4r-\\d+-", buffer_size=undef, quiet=undef, expect_not_found=0, record_output=1, no_regex=0, timeout=90)
[2024-01-16T11:45:47.235577-05:00] [debug] [pid:10982] >>> testapi::wait_serial: SCRIPT_FINISHEDqQf4r-\d+-: ok
[2024-01-16T11:45:47.235785-05:00] [debug] [pid:10982] tests/network/setup_multimachine.pm:45 called mm_network::setup_static_mm_network -> lib/mm_network.pm:228 called mm_network::configure_static_dns -> lib/mm_
network.pm:132 called testapi::assert_script_run
[2024-01-16T11:45:47.235910-05:00] [debug] [pid:10982] <<< testapi::assert_script_run(cmd="nmcli connection modify 'Welcome to openSUSE Tumbleweed 20240115 - Kernel 6.6.11-1-default (ttyS0).\n\nens4: 10.0.2.102 f
e80::5054:ff:fe12:2\n\n\nsusetest login: ens4' ipv4.dns '10.0.2.3'", quiet=undef, fail_message="", timeout=90)
[2024-01-16T11:45:47.236029-05:00] [debug] [pid:10982] tests/network/setup_multimachine.pm:45 called mm_network::setup_static_mm_network -> lib/mm_network.pm:228 called mm_network::configure_static_dns -> lib/mm_
network.pm:132 called testapi::assert_script_run
[2024-01-16T11:45:47.236129-05:00] [debug] [pid:10982] <<< testapi::type_string(string="nmcli connection modify 'Welcome to openSUSE Tumbleweed 20240115 - Kernel 6.6.11-1-default (ttyS0).\n\nens4: 10.0.2.102 fe80
::5054:ff:fe12:2\n\n\nsusetest login: ens4' ipv4.dns '10.0.2.3'", max_interval=250, wait_screen_change=0, wait_still_screen=0, timeout=30, similarity_level=47)
[2024-01-16T11:45:53.755719-05:00] [debug] [pid:10982] tests/network/setup_multimachine.pm:45 called mm_network::setup_static_mm_network -> lib/mm_network.pm:228 called mm_network::configure_static_dns -> lib/mm_
network.pm:132 called testapi::assert_script_run
[2024-01-16T11:45:53.758424-05:00] [debug] [pid:10982] <<< testapi::type_string(string="; echo Q94Z9-\$?- > /dev/ttyS0\n", max_interval=250, wait_screen_change=0, wait_still_screen=0, timeout=30, similarity_level
=47)
[2024-01-16T11:45:54.885176-05:00] [debug] [pid:10982] tests/network/setup_multimachine.pm:45 called mm_network::setup_static_mm_network -> lib/mm_network.pm:228 called mm_network::configure_static_dns -> lib/mm_
network.pm:132 called testapi::assert_script_run
[2024-01-16T11:45:54.885778-05:00] [debug] [pid:10982] <<< testapi::wait_serial(regexp=qr/Q94Z9-\d+-/u, quiet=undef, buffer_size=undef, expect_not_found=0, timeout=90, no_regex=0, record_output=undef)
[2024-01-16T11:45:56.941627-05:00] [debug] [pid:10982] >>> testapi::wait_serial: (?^u:Q94Z9-\d+-): ok
[2024-01-16T11:45:56.998284-05:00] [info] [pid:10982] ::: basetest::runtest: # Test died: command 'nmcli connection modify 'Welcome to openSUSE Tumbleweed 20240115 - Kernel 6.6.11-1-default (ttyS0).
ens4: 10.0.2.102 fe80::5054:ff:fe12:2
susetest login: ens4' ipv4.dns '10.0.2.3'' failed at /usr/lib/os-autoinst/testapi.pm line 926.
testapi::assert_script_run("nmcli connection modify 'Welcome to openSUSE Tumbleweed 20240"...) called at opensuse/lib/mm_network.pm line 132
mm_network::configure_static_dns(HASH(0x563622f61c98), "is_nm", 1) called at opensuse/lib/mm_network.pm line 228
mm_network::setup_static_mm_network("10.0.2.102/24") called at opensuse/tests/network/setup_multimachine.pm line 45
setup_multimachine::run(setup_multimachine=HASH(0x563626081bd0)) called at /usr/lib/os-autoinst/basetest.pm line 352
eval {...} called at /usr/lib/os-autoinst/basetest.pm line 346
basetest::runtest(setup_multimachine=HASH(0x563626081bd0)) called at /usr/lib/os-autoinst/autotest.pm line 415
eval {...} called at /usr/lib/os-autoinst/autotest.pm line 415
autotest::runalltests() called at /usr/lib/os-autoinst/autotest.pm line 272
eval {...} called at /usr/lib/os-autoinst/autotest.pm line 272
autotest::run_all() called at /usr/lib/os-autoinst/autotest.pm line 323
autotest::__ANON__(Mojo::IOLoop::ReadWriteProcess=HASH(0x563627209df0)) called at /usr/lib/perl5/vendor_perl/5.38.2/Mojo/IOLoop/ReadWriteProcess.pm line 329
eval {...} called at /usr/lib/perl5/vendor_perl/5.38.2/Mojo/IOLoop/ReadWriteProcess.pm line 329
Mojo::IOLoop::ReadWriteProcess::_fork(Mojo::IOLoop::ReadWriteProcess=HASH(0x563627209df0), CODE(0x56362720a060)) called at /usr/lib/perl5/vendor_perl/5.38.2/Mojo/IOLoop/ReadWriteProcess.pm line 492
Mojo::IOLoop::ReadWriteProcess::start(Mojo::IOLoop::ReadWriteProcess=HASH(0x563627209df0)) called at /usr/lib/os-autoinst/autotest.pm line 325
autotest::start_process() called at /usr/lib/os-autoinst/OpenQA/Isotovideo/Runner.pm line 94
OpenQA::Isotovideo::Runner::start_autotest(OpenQA::Isotovideo::Runner=HASH(0x563621c6b1d0)) called at /usr/bin/isotovideo line 192
eval {...} called at /usr/bin/isotovideo line 181
</code></pre> openQA Infrastructure - action #152503 (Resolved): [FIRING:1] worker38 (worker38: partitions usag...https://progress.opensuse.org/issues/1525032023-12-12T14:05:07Zdheidlerdheidler@suse.com
<p>On 12.12.2023 11:15 CET.</p>
<p><a href="http://stats.openqa-monitor.qa.suse.de/alerting/grafana/partitions_usage_alert_worker38/view?orgId=1" class="external">http://stats.openqa-monitor.qa.suse.de/alerting/grafana/partitions_usage_alert_worker38/view?orgId=1</a></p>
<p>Maybe an issue with a partly crashed workercache service or a job with to too large disk size.</p>
<p>Also interesting:<br>
br1 out peaked short of 6GB/s around that time:<br>
<a href="https://stats.openqa-monitor.qa.suse.de/d/WDworker38/worker-dashboard-worker38?orgId=1&from=1702374388707&to=1702374657861&viewPanel=42026" class="external">https://stats.openqa-monitor.qa.suse.de/d/WDworker38/worker-dashboard-worker38?orgId=1&from=1702374388707&to=1702374657861&viewPanel=42026</a></p>
openQA Project - action #152287 (Resolved): [FIRING:1] (Packet loss between worker hosts and othe...https://progress.opensuse.org/issues/1522872023-12-08T11:13:40Zdheidlerdheidler@suse.com
<p>Seems that this VM was removed by infra due to maxtorhof decommission,<br>
as that host was used to reach IPMI interfaces of hosts in NUE1-serverroom1.</p>
openQA Infrastructure - action #130210 (Resolved): [FIRING:1] Packet loss between worker hosts an...https://progress.opensuse.org/issues/1302102023-06-01T09:27:50Zdheidlerdheidler@suse.com
<p>The grafana alert fired at 31.05. 07:37 and is still firing as of 01.06. 11:27.</p>
<p><a href="https://stats.openqa-monitor.qa.suse.de/alerting/grafana/2Z025iB4km/view?orgId=1" class="external">https://stats.openqa-monitor.qa.suse.de/alerting/grafana/2Z025iB4km/view?orgId=1</a></p>
openQA Project - action #105855 (Resolved): [easy][beginner] openqa-worker@.service should handle...https://progress.opensuse.org/issues/1058552022-02-02T16:31:12Zdheidlerdheidler@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<pre><code>-- Logs begin at Thu 2022-01-06 12:00:01 UTC, end at Wed 2022-02-02 16:18:15 UTC. --
Jan 06 12:00:37 localhost systemd[1]: Starting openQA Worker #4...
Jan 06 12:00:37 localhost systemd[1]: Started openQA Worker #4.
Jan 06 12:00:40 localhost worker[1306]: [info] worker 4:
Jan 06 12:00:40 localhost worker[1306]: - config file: /etc/openqa/workers.ini
Jan 06 12:00:40 localhost worker[1306]: - worker hostname: localhost
Jan 06 12:00:40 localhost worker[1306]: - isotovideo version: 24
Jan 06 12:00:40 localhost worker[1306]: - websocket API version: 1
Jan 06 12:00:40 localhost worker[1306]: - web UI hosts: http://10.131.0.32
Jan 06 12:00:40 localhost worker[1306]: - class: generalhw_RPi4
Jan 06 12:00:40 localhost worker[1306]: - no cleanup: no
Jan 06 12:00:40 localhost worker[1306]: - pool directory: /var/lib/openqa/pool/4
Jan 06 12:00:40 localhost worker[1306]: [info] Project dir for host http://10.131.0.32 is /var/lib/openqa/share
Jan 06 12:00:40 localhost worker[1306]: [info] Registering with openQA http://10.131.0.32
Jan 06 12:00:40 localhost worker[1306]: [error] Failed to register at http://10.131.0.32 - 403 response: timestamp mismatch - ignoring server
Jan 06 12:00:40 localhost worker[1306]: [error] Stopping because registration with all configured web UI hosts failed
Jan 06 12:00:40 localhost systemd[1]: openqa-worker@4.service: Succeeded.
</code></pre>
<p>This worker is running on a raspberry pi without a real time clock.<br>
The output is from today (Feb 02) and chronyd is enabled on that machine.<br>
Still the worker doesn't come up because the worker is started before NTP sync is done.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> openQA worker does not fail with an error and does not report an error when a time source is not (yet) available</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Make the code itself resilient to time not being available yet, e.g. just wait until it becomes available</li>
</ul>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>entrance level issue</p>
openQA Tests - action #64370 (Rejected): [functiona][u] test fails in kdump_and_crash: Fail in Op...https://progress.opensuse.org/issues/643702020-03-10T15:53:32Zdheidlerdheidler@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP2-Online-ppc64le-toolchain_zypper@ppc64le fails in<br>
<a href="https://openqa.suse.de/tests/3976439/modules/kdump_and_crash/steps/46" class="external">kdump_and_crash</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Maintainer: mnowak, okurz</p>
<p>Install toolchain packages and test the toolchain. Uses a more powerful machine configuration.</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/3976439" class="external">153.7</a> (current job)</p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: <a href="https://openqa.suse.de/tests/3974136" class="external">154.1</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=ppc64le&distri=sle&flavor=Online&machine=ppc64le&test=toolchain_zypper&version=15-SP2" class="external">latest</a></p>
openQA Tests - action #62429 (Resolved): [functional][u] Fix test modules that are not in lib dir...https://progress.opensuse.org/issues/624292020-01-21T10:01:24Zdheidlerdheidler@suse.com
<p>You can find which modules are affected by removing <code>^use (base )?\"?$t\"?)</code> from <code>tools/detect_unused_modules</code> and run that tool.<br>
It should report all related modules.</p>
<ul>
<li><strong>AC1</strong>: <code>^use (base )?\"?$t\"?)</code> is removed from <code>tools/detect_unused_modules</code> to prevent further use of the wrong directory</li>
<li><strong>AC2</strong>: All existing baseclasses and libs are moved to lib directory.</li>
</ul>
openQA Tests - action #54857 (Rejected): [functiona][u][sporadic] test fails in apache_ssl: gener...https://progress.opensuse.org/issues/548572019-07-30T11:57:40Zdheidlerdheidler@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-12-SP5-Server-DVD-aarch64-textmode+proxy_SCC@aarch64 fails in<br>
<a href="https://openqa.suse.de/tests/3166512/modules/apache_ssl/steps/10" class="external">apache_ssl</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>jpupava: Also test invalid SCC URL <a href="https://trello.com/c/N09TRZxX/968-3-don-t-crash-on-invalid-regurl-on-linuxrc-commandline" class="external">https://trello.com/c/N09TRZxX/968-3-don-t-crash-on-invalid-regurl-on-linuxrc-commandline</a></p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/3166512" class="external">0251</a> (current job)</p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: <a href="https://openqa.suse.de/tests/3155125" class="external">0248</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?test=textmode%2Bproxy_SCC&version=12-SP5&machine=aarch64&distri=sle&flavor=Server-DVD&arch=aarch64" class="external">latest</a></p>
openQA Project - action #49070 (Resolved): [functional][u] hovering +1 next to a failed test suit...https://progress.opensuse.org/issues/490702019-03-12T12:58:21Zdheidlerdheidler@suse.com
<p>When you hover the +1 or +2 or +n next to a red bubble with more than one failing module should show the remaining failed modules.<br>
Eg here: <a href="https://openqa.suse.de/tests/2521991#next_previous" class="external">https://openqa.suse.de/tests/2521991#next_previous</a></p>
openQA Project - action #44399 (New): [easy][beginner] Fix assert_script_sudo and script_sudo bei...https://progress.opensuse.org/issues/443992018-11-27T13:55:41Zdheidlerdheidler@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>Found working on: <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: [functional][u] openssh: test needs to use key-based login for root (Resolved)" href="https://progress.opensuse.org/issues/43703">#43703</a></p>
<p>When calling <code>script_sudo</code> or <code>assert_script_sudo</code> as root (eg to avoid code duplication) it fails as openQA expects a password prompt that doesn't appear when the shell is already a root-shell:</p>
<p>To show this issue I just added this two lines to the top of a test module:</p>
<pre><code>select_console 'root-console';
assert_script_sudo 'whoami';
</code></pre>
<p><a href="http://artemis.suse.de/tests/1007#step/rsync/10" class="external">http://artemis.suse.de/tests/1007#step/rsync/10</a></p>
<p>Expected result: openQA should gracefully handle this.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> <strong>assert_script_sudo</strong> can be run when current user is root.</li>
<li><strong>AC2:</strong> Duplicate code is adapted (like <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6270" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6270</a>)</li>
</ul>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>entrance level issue</p>
openQA Project - action #38486 (Rejected): [functional][u] add capability flags to os-autoinst ba...https://progress.opensuse.org/issues/384862018-07-17T15:23:16Zdheidlerdheidler@suse.com
<p>In <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/lib/main_common.pm#L885" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/lib/main_common.pm#L885</a> (for example) we have many checks on the name of the backend. This is getting more and more hard to read.<br>
It could be easier to use capability flags in the backends and do the decisions based on this flags.</p>
openQA Tests - action #38204 (Resolved): [functional] self-tests for https://gitlab.suse.de/openq...https://progress.opensuse.org/issues/382042018-07-04T12:07:26Zdheidlerdheidler@suse.com
<p>Deploy the testsuite from <a href="https://progress.opensuse.org/issues/36523" class="external">https://progress.opensuse.org/issues/36523</a> for internal git as well.</p>
openQA Tests - action #37495 (Resolved): [functional][u] Better explicit tests for pkcon as well ...https://progress.opensuse.org/issues/374952018-06-19T08:13:07Zdheidlerdheidler@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario opensuse-15.0-DVD-aarch64-kde@aarch64 fails in<br>
<a href="https://openqa.opensuse.org/tests/693593/modules/amarok/steps/13" class="external">amarok</a><br>
with a confusing show of screenshots.<br>
You see in <a href="https://openqa.opensuse.org/tests/693593#step/amarok/11" class="external">https://openqa.opensuse.org/tests/693593#step/amarok/11</a> that the prompt shows up. After that the password is actually typed. Then in <a href="https://openqa.opensuse.org/tests/693593#step/amarok/12" class="external">https://openqa.opensuse.org/tests/693593#step/amarok/12</a> it looks like the same window is still there but it is <em>not the same window</em>. It is popping up <em>again</em>. The real error message can be seen in the background xterm window, amarok could simply not be installed.<br>
The actual problem "requires taglib >= 1.7 but this requirement can not be provided"</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> The error that the package is not installable is made obvious</li>
<li><strong>AC2:</strong> Also in this case we would fall back to zypper</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>See ACs</li>
<li>Also think about removing the for loop because it seems to not help as expected and rather hides real errors</li>
</ul>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.opensuse.org/tests/latest?flavor=DVD&version=15.0&distri=opensuse&arch=aarch64&test=kde&machine=aarch64" class="external">latest</a></p>
openQA Project - coordination #13812 (New): [epic][dashboard] openQA Dashboard ideashttps://progress.opensuse.org/issues/138122016-09-19T11:38:34Zdheidlerdheidler@suse.com
<a name="Related-use-cases"></a>
<h2 >Related <a href="https://progress.opensuse.org/projects/openqav3/wiki/#Use-cases" class="external">use cases</a><a href="#Related-use-cases" class="wiki-anchor">¶</a></h2>
<p>Especially <a href="https://progress.opensuse.org/projects/openqav3/wiki/#Use-case-1" class="external">UC1</a> and <a href="https://progress.opensuse.org/projects/openqav3/wiki/#Use-case-5" class="external">UC5</a></p>
<a name="ideas"></a>
<h2 >ideas<a href="#ideas" class="wiki-anchor">¶</a></h2>
<ul>
<li>Failing tests
<ul>
<li>with unassigned ticket -> currently implemented as <a href="https://w3.nue.suse.com/~okurz/openqa_suse_de_status.html#unassigned_box" class="external">unassigned report</a></li>
<li>with resolved / closed ticket (also see <a class="issue tracker-4 status-3 priority-5 priority-high3 closed parent" title="action: [tools][dashboard][Feature] - make openQA show when a bug is marked as "RESOLVED FIXED" but still... (Resolved)" href="https://progress.opensuse.org/issues/12092">#12092</a>)</li>
<li>related ticket: <a class="issue tracker-4 status-3 priority-4 priority-default closed child" title="action: [tools][dashboard]Tracking open bugs based on product (Resolved)" href="https://progress.opensuse.org/issues/10188">#10188</a></li>
</ul></li>
<li>Consider some testsuites as more important than other testsuites <a class="issue tracker-4 status-6 priority-4 priority-default closed" title="action: [tools][dashboard]Level of importance of test_suites + architectures (Rejected)" href="https://progress.opensuse.org/issues/13780">#13780</a></li>
<li>Filter on index page for specific groups -> <a href="https://github.com/os-autoinst/openQA/pull/923" class="external">gh#923</a></li>
<li>Group test results by build number, related ticked: <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: meta job groups and nested groups (Resolved)" href="https://progress.opensuse.org/issues/13742">#13742</a></li>
<li>finish at least one build per day -> Current workflow: QA reviewer decides this and can mark one build as important, feature request <a class="issue tracker-4 status-3 priority-4 priority-default closed child" title="action: [tools]finish at least one build per day (Resolved)" href="https://progress.opensuse.org/issues/15844">#15844</a></li>
<li>priority of bugs in review reports -> <a href="https://github.com/okurz/openqa_review/pull/25" class="external">openqa_review#25</a></li>
<li>on index page add link to filter box (down) because "no one scrolls down" -> <a href="https://gitlab.suse.de/openqa/salt-states-openqa/merge_requests/19">https://gitlab.suse.de/openqa/salt-states-openqa/merge_requests/19</a></li>
<li>"milestones" as special tags (asked by ast) -> <a href="http://open.qa/docs/#_tag_builds_with_special_comments_on_group_overview">http://open.qa/docs/#_tag_builds_with_special_comments_on_group_overview</a></li>
<li>special mode of Dashboard mode which allow to see summary of all job groups in optimized to full screen view <a class="issue tracker-4 status-3 priority-3 priority-lowest closed child" title="action: [dashboard] Create full screen view for openQA dashboard (Resolved)" href="https://progress.opensuse.org/issues/17886">#17886</a></li>
<li>Statistics over
<ul>
<li>failed/passed ratio per build for each product</li>
<li>number of executed testsuites per build for each product</li>
</ul></li>
<li>List overall "todo: review" entries</li>
<li>Overall status indicator (eg. status light / 'Ampel')</li>
<li>"the oldest still open bug"</li>
<li>"the most flaky scenario / module / architecture"</li>
<li>back-references to bugs
<ul>
<li>"reverse" carry over: when old job failed and new job passed -> post comment into bug that would have been carried over to new job if it would have failed (related to <a href="https://wiki.microfocus.net/index.php?title=User:Okurz#Review_of_bugs_.22RESOLVED_FIXED.2C_NOT_VERIFIED.22" class="external">okurz wiki</a> )</li>
</ul></li>
<li>scenario result and state change in each tests result</li>
<li>track all changes (eg. infrastructure, test changed, product changed, ...)</li>
<li>measure completion time of builds, also per architecture</li>
<li>tests that have not run for long time</li>
<li>live update of bug status (e.g. subscribe a special user to email and trigger events based on email reception)</li>
<li>personal customized view vs. static hierarchical dashboard view</li>
<li>"weather of scenario", e.g. is it failing all the time or just sporadically</li>
<li>better integration of status from external jobs and testing systems (see <a href="#better-integration-of-status-from-external-jobs-and-testing-systems" class="external">below</a>)</li>
<li>customized, personal filter pre-saved</li>
<li>dheidler: learn about bugzilla integration in "smash" (e.g. ask tgoettlicher)</li>
</ul>
<a name="implementation-ideas"></a>
<h2 >implementation ideas<a href="#implementation-ideas" class="wiki-anchor">¶</a></h2>
<a name="better-integration-of-status-from-external-jobs-and-testing-systems"></a>
<h3 >better integration of status from external jobs and testing systems<a href="#better-integration-of-status-from-external-jobs-and-testing-systems" class="wiki-anchor">¶</a></h3>
<p>To use openQA also as the main reporting platform relying on other tools we have in our infrastructure (at SUSE) there are already test runners feeding back the information e.g. in junit format. Also, using the client script jobs can be started and their result set along with comments, e.g. for tags. Example:</p>
<pre><code>job_id=$(client --host http://localhost jobs post TEST=foo_external _GROUP="openSUSE Tumbleweed AArch64" BUILD=1 | sed -n 's/^{ id => \([0-9]\+\) }$/\1/p')
client --host http://localhost jobs/${job_id}/set_done post result=passed
client --host http://localhost jobs/${job_id}/comments post text=bsc#1234
</code></pre>
<a name="references"></a>
<h2 >references<a href="#references" class="wiki-anchor">¶</a></h2>
<p>could be inspired by sonar, e.g. see <a href="https://sonarqube.com/">https://sonarqube.com/</a> and <a href="https://sonarqube.com/dashboard?id=c-family%3ASamba&did=148">https://sonarqube.com/dashboard?id=c-family%3ASamba&did=148</a>, but also <a href="https://wiki.jenkins-ci.org/pages/viewpage.action?pageId=69763309" class="external">jenkins Radiator View Plugin</a> or <a href="https://wiki.jenkins-ci.org/display/JENKINS/eXtreme+Feedback+Panel+Plugin" class="external">jenkins eXtreme Feedback Panel Plugin</a> or <a href="https://jenkins.io/blog/2016/01/10/beautiful-jenkins-dashboard/">https://jenkins.io/blog/2016/01/10/beautiful-jenkins-dashboard/</a> <br>
… or <a href="https://github.com/influxdata/chronograf">https://github.com/influxdata/chronograf</a></p>
<p>And don't forget about <a href="http://testsuites.qa.suse.cz">http://testsuites.qa.suse.cz</a> -> dead by now</p>