openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842022-03-18T07:25:12ZopenSUSE Project Management Tool
Redmine openQA Project - action #108554 (New): [ux][ui] Wrong formatting on some links in single quotes i...https://progress.opensuse.org/issues/1085542022-03-18T07:25:12ZVANASTASIADISvasilios.anastasiadis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>When trying to use <code>openqa-clone-custom-git-refspec</code> with <code>NEEDLES_GIT_REFSPEC</code>, openqa is unable to use the needle's link. In the details of the failed job, in the spot where it mentions the problem, it includes that link inside quotes as information. However, clicking on the link to open it includes the trailing quote in the address, leading to a 404 response (which can be fixed by manually removing the trailing quote in the address bar).</p>
<p>An example of this can be observed <a href="https://openqa.suse.de/tests/8340493" class="external">here</a>. Near the bottom of the page, there are 3 occurrences of the link '<a href="https://gitlab.suse.de/VANASTASIADIS/os-autoinst-needles-sles/tree/imagemagick_needles" class="external">https://gitlab.suse.de/VANASTASIADIS/os-autoinst-needles-sles/tree/imagemagick_needles</a>'. All three lead to a 404 page, but removing the trailing quote leads to the correct page.</p>
<a name="Steps-to-reproduce"></a>
<h2 >Steps to reproduce<a href="#Steps-to-reproduce" class="wiki-anchor">¶</a></h2>
<ul>
<li>Run
<code>
openqa-clone-custom-git-refspec <valid pr link> <valid job-to-clone link> MAX_JOB_TIME=7593869 NEEDLES_GIT_REFSPEC=<valid needle branch link> _GROUP=0 _SKIP_POST_FAIL_HOOKS=1
</code></li>
<li>Go to the resulting openqa link and wait until the job fails</li>
<li>Go near the bottom of the screen and click on the needle link</li>
</ul>
<a name="Problem"></a>
<h2 >Problem<a href="#Problem" class="wiki-anchor">¶</a></h2>
<p>It seems to be a formatting problem, and it's probably not affecting the actual use of the link in the code, as the opening quote exists too and is not part of the link. It should however be ensured that this is the case.</p>
<a name="Suggestion"></a>
<h2 >Suggestion<a href="#Suggestion" class="wiki-anchor">¶</a></h2>
<ul>
<li>ensure it is a pure formatting bug</li>
<li>locate corresponding code</li>
<li>fix it so trailing quotes are not part of the link</li>
</ul>
<p>openqa-clone-custom-git-refspec MAX_JOB_TIME=7593869 NEEDLES_GIT_REFSPEC= _GROUP=0 _SKIP_POST_FAIL_HOOKS=1</p>
QA - action #98997 (Resolved): [tools] [smelt] [python3.6] Replace all older text formatting with...https://progress.opensuse.org/issues/989972021-09-21T11:41:48ZVANASTASIADISvasilios.anastasiadis@suse.com
<a name="User-story"></a>
<h2 >User story<a href="#User-story" class="wiki-anchor">¶</a></h2>
<p>The python linter now gives warnings against the use of the old <code>.format()</code> method of formatting strings, proposing the use of <a href="https://www.python.org/dev/peps/pep-0498/" class="external">f-strings</a>, as they are faster and more readable. This has caused the smelt pipelines to fail. Instead of removing the warning, it's a better idea to use f-strings where applicable.</p>
<p>Related ticket: <a href="https://gitlab.suse.de/tools/smelt/-/issues/730" class="external">https://gitlab.suse.de/tools/smelt/-/issues/730</a></p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> All uses of the old formatting method that make sense to be replaced by f-strings are replaced</li>
<li><strong>AC2:</strong> The SMELT pipelines pass without pylint failing due to <code>consider-f-strings</code> warning</li>
</ul>
<a name="Tasks"></a>
<h2 >Tasks<a href="#Tasks" class="wiki-anchor">¶</a></h2>
<ul>
<li>see failing pipeline results for places to switch to f-strings (i.e. <a href="https://gitlab.suse.de/tools/smelt/-/jobs/595135" class="external">https://gitlab.suse.de/tools/smelt/-/jobs/595135</a>)</li>
<li>replace <code>.format()</code> occurrences with f-strings, consider the best way to accurately do so so that the behaviour doesn't change</li>
</ul>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Open mr at <a href="https://gitlab.suse.de/tools/smelt/-/merge_requests/782" class="external">https://gitlab.suse.de/tools/smelt/-/merge_requests/782</a></p>
openQA Project - action #98604 (Resolved): Provide data about ratio of automatically approved SLE...https://progress.opensuse.org/issues/986042021-09-14T12:20:32ZVANASTASIADISvasilios.anastasiadis@suse.com
<a name="User-story"></a>
<h2 >User story<a href="#User-story" class="wiki-anchor">¶</a></h2>
<p>In order to have a better overview of our automatic testing procedures and improve our workflows, we need to know what percentage of tests fail and why. This should ideally be <10% under normal circumstances, so if we have a lot of test failures that then need manual intervention we should investigate why this happens and how to fix it.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong>: data about the percentage of automatically approved incidents exist</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>read data from smelt, i.e. <a href="https://tools.io.suse.de/smelt/user/api/" class="external">https://tools.io.suse.de/smelt/user/api/</a></li>
<li>gather the data in human readable format</li>
</ul>
openQA Project - action #98186 (Resolved): Backlog checker does not take `QA` project issues into...https://progress.opensuse.org/issues/981862021-09-06T09:49:05ZVANASTASIADISvasilios.anastasiadis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>The queries in the <code>untriaged_QA</code> and <code>untriaged_tools</code> checks in <a href="https://github.com/os-autoinst/qa-tools-backlog-assistant" class="external">https://github.com/os-autoinst/qa-tools-backlog-assistant</a> don't take into account <code>QA</code> tickets, only <code>openQA project</code> and <code>openQA infrastructure</code>. </p>
<a name="Steps-to-reproduce"></a>
<h2 >Steps to reproduce<a href="#Steps-to-reproduce" class="wiki-anchor">¶</a></h2>
<ul>
<li>Check if there is any untriaged (as in not assigned a target version) under <code>QA</code></li>
<li>Check the relevant untriaged query in progress (<a href="https://progress.opensuse.org/projects/qa/issues?query_id=576" class="external">https://progress.opensuse.org/projects/qa/issues?query_id=576</a>). It will appear here</li>
<li>Check the backlog checker in <a href="https://github.com/os-autoinst/qa-tools-backlog-assistant" class="external">https://github.com/os-autoinst/qa-tools-backlog-assistant</a>. It shouldn't appear here.</li>
</ul>
<a name="Problem"></a>
<h2 >Problem<a href="#Problem" class="wiki-anchor">¶</a></h2>
<p>The query only searches for <code>openQA Project</code> and <code>openQA Infrastructure</code> tickets, not <code>QA</code></p>
<a name="Suggestion"></a>
<h2 >Suggestion<a href="#Suggestion" class="wiki-anchor">¶</a></h2>
<ul>
<li>Fix the query in <a href="https://github.com/os-autoinst/qa-tools-backlog-assistant/blob/master/backlog_checker.py" class="external">https://github.com/os-autoinst/qa-tools-backlog-assistant/blob/master/backlog_checker.py</a> to display the appropriate results. Another query for id 115, identical to the other two for <code>untriaged_qa</code> and <code>untriaged_tools</code> functions should do the trick.</li>
</ul>
openQA Project - action #97580 (Resolved): Automatic check for qa-tools backlog limits in Github ...https://progress.opensuse.org/issues/975802021-08-27T10:13:03ZVANASTASIADISvasilios.anastasiadis@suse.com
<a name="User-story"></a>
<h2 >User story<a href="#User-story" class="wiki-anchor">¶</a></h2>
<p>Instead of manually accessing the custom queries defined in <a href="https://progress.opensuse.org/projects/qa/wiki/#Target-numbers-or-guideline-should-be-in-priorities" class="external">https://progress.opensuse.org/projects/qa/wiki/#Target-numbers-or-guideline-should-be-in-priorities</a>, it would be nice to have automatic checks for those in a gh actions workflow.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> A scheduled Github Actions workflow exists that fails when the target numbers for any one of the defined queries are not met</li>
<li><strong>AC2:</strong> Consider if any further action would be desired (like an alert in case of target numbers not being met)</li>
</ul>
<a name="Tasks"></a>
<h2 >Tasks<a href="#Tasks" class="wiki-anchor">¶</a></h2>
<ul>
<li>Create a gh action workflow with individual checks for each query in <a href="https://progress.opensuse.org/projects/qa/wiki/#Target-numbers-or-guideline-should-be-in-priorities" class="external">https://progress.opensuse.org/projects/qa/wiki/#Target-numbers-or-guideline-should-be-in-priorities</a></li>
<li>Evaluate if there's a need for further actions</li>
</ul>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>A POC exists here: <a href="https://github.com/BillAnastasiadis/qa-tools-backlog-assistant/actions" class="external">https://github.com/BillAnastasiadis/qa-tools-backlog-assistant/actions</a></p>
QA - action #97505 (New): [qem][tools] embed important IBS comments in the testreportshttps://progress.opensuse.org/issues/975052021-08-25T09:35:26ZVANASTASIADISvasilios.anastasiadis@suse.com
<a name="User-story"></a>
<h2 >User story<a href="#User-story" class="wiki-anchor">¶</a></h2>
<p>Occasionally, engineers from security or coordination want to communicate special information about specific requests to testers. This is already done in the form of IBS comments with specific tags, but since most testers do not check ibs and ibs comments, it would be convenient to have those comments displayed in the testreport.</p>
<p>IBS comments containing important information aimed at the testers always start with <code>QA HINT</code> or <code>QA-HINT</code>. Embedding those comments only should be sufficient.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> comments starting with <code>QA HINT</code> or <code>QA-HINT</code> are copied in the testreport</li>
<li><strong>AC2:</strong> comments are placed somewhere easily noticed by the tester before they start reviewing the request</li>
</ul>
<a name="Tasks"></a>
<h2 >Tasks<a href="#Tasks" class="wiki-anchor">¶</a></h2>
<ul>
<li>decide where inside the testreport to place the comments </li>
<li>fetch and copy the specified IBS comments to the testreport in the decided location</li>
</ul>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>In addition to this, there is a SMELT ticket to highlight such comments in smelt (<a href="https://gitlab.suse.de/tools/smelt/-/issues/720" class="external">https://gitlab.suse.de/tools/smelt/-/issues/720</a>). </p>
openQA Project - action #97454 (New): Decide and implement predefined tags for the commit message...https://progress.opensuse.org/issues/974542021-08-24T08:00:19ZVANASTASIADISvasilios.anastasiadis@suse.com
<a name="User-story"></a>
<h2 >User story<a href="#User-story" class="wiki-anchor">¶</a></h2>
<p>When a user constructs a commit message, there should be a predefined list of accepted tags that can be used. The use of tags provides clarity about the domain the pull request touches upon, and users should not be free to put arbitrary tags there.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> the tag list has been decided and agreed upon</li>
<li><strong>AC2:</strong> the tag list is implemented in the commit message checker and merged</li>
</ul>
<a name="Tasks"></a>
<h2 >Tasks<a href="#Tasks" class="wiki-anchor">¶</a></h2>
<ul>
<li>propose useful tags (better here, in written form)</li>
<li>if needed, decide the final list in a meeting (daily or weekly should be fine, no dedicated call needed)</li>
<li>implement what is decided</li>
</ul>
QA - action #95503 (Resolved): qam.suse.de api returns 500(Internal Server Error) for requests wi...https://progress.opensuse.org/issues/955032021-07-14T11:41:32ZVANASTASIADISvasilios.anastasiadis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>See ticket in parent tracker: <a href="https://gitlab.suse.de/qa-maintenance/qamapi/-/issues/5" class="external">https://gitlab.suse.de/qa-maintenance/qamapi/-/issues/5</a></p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><<strong>AC1:</strong> the api doesn't fail to return a testreport when the reviewer's name isn't preceded by a space in the relevant line of the testreport</li>
</ul>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>This bug leaves otherwise valid testreports unable to be queried by the API, which also impacts the Maintenance Testreports section of <a href="https://smelt.suse.de/reports/" class="external">https://smelt.suse.de/reports/</a></p>
QA - action #94486 (Resolved): Complete and deploy testreport db and page on smelthttps://progress.opensuse.org/issues/944862021-06-22T12:30:29ZVANASTASIADISvasilios.anastasiadis@suse.com
<a name="User-story"></a>
<h2 >User story<a href="#User-story" class="wiki-anchor">¶</a></h2>
<p>Data from testreports are provided by qam.suse.de only in a per-testreport basis. This feature will give users the ability to look at combined data and statistics based on a set of testreports of their choice, by importing the data from qam.suse.de api to smelt and creating a page for their visualization.</p>
<ul>
<li>Related gitlab ticket:<a href="https://gitlab.suse.de/tools/smelt/-/issues/501" class="external">https://gitlab.suse.de/tools/smelt/-/issues/501</a></li>
<li>Related mr: <a href="https://gitlab.suse.de/tools/smelt/-/merge_requests/588" class="external">https://gitlab.suse.de/tools/smelt/-/merge_requests/588</a></li>
</ul>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> The data is accurately imported in smelt in realtime</li>
<li><strong>AC2:</strong> The data are correctly displayed in the related reports page</li>
</ul>
<a name="Tasks"></a>
<h2 >Tasks<a href="#Tasks" class="wiki-anchor">¶</a></h2>
<ul>
<li>Add realtime db population functionality</li>
<li>Add performance and readability improvements</li>
</ul>
QA - action #94246 (Resolved): Collect data on update/packages and maintenance workload for 2020/...https://progress.opensuse.org/issues/942462021-06-18T09:15:36ZVANASTASIADISvasilios.anastasiadis@suse.com
<a name="User-story"></a>
<h2 >User story<a href="#User-story" class="wiki-anchor">¶</a></h2>
<p>Collect data on number of packages, both kernel related and others, number of packages per Release Request testing and processing times of Release Requests, security updates for QE Maintenance. Period of interest is 2020 and 2021. Requested by Zoltan Balogh.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<p><em>AC1:</em>* Provide the requested data to Zoltan.</p>
<a name="Tasks"></a>
<h2 >Tasks<a href="#Tasks" class="wiki-anchor">¶</a></h2>
<ul>
<li>Use maintenancetrends page from SMELT to get testing time data</li>
<li>Use direct SQL queries on the SMELT db to acquire other data</li>
<li>Modify the maintenancetrends page to get specific results if needed</li>
</ul>
openQA Project - action #93811 (Resolved): [timeboxed:20h] vanastasiadis: Learn about Perl and Pe...https://progress.opensuse.org/issues/938112021-06-10T11:42:34ZVANASTASIADISvasilios.anastasiadis@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>As a member of the qa-tools squad, I want to teach myself how to program in perl as well as best practices, in order to be able to contribute in all aspects of openQA development.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong>Know the basics and best practices of Perl programming and be able to write sufficiently complex code</li>
<li><strong>AC2:</strong> Be able to read and understand existing Perl code in openQA repositories</li>
</ul>
<a name="Tasks"></a>
<h2 >Tasks<a href="#Tasks" class="wiki-anchor">¶</a></h2>
<ul>
<li>read <a href="http://modernperlbooks.com/books/modern_perl_2016/index.html" class="external">http://modernperlbooks.com/books/modern_perl_2016/index.html</a> (suggestion by okurz)</li>
<li>test acquired knowledge by examining openQA code</li>
</ul>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Everyone who wishes to contribute learning/training resources regarding Perl can do so in the comments.</p>
openQA Project - action #92497 (Resolved): Perl test execution in os-autoinst runs succesfully bu...https://progress.opensuse.org/issues/924972021-05-11T12:24:00ZVANASTASIADISvasilios.anastasiadis@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>When running a single perl test (or a series of tests), following the steps described in <a href="https://github.com/os-autoinst/os-autoinst#conducting-the-build">https://github.com/os-autoinst/os-autoinst#conducting-the-build</a>, the tests run as expected, but afterwards encounters the following error and exits:</p>
<pre><code class="text syntaxhl" data-language="text">Cannot detect source of '17-basetest.t'! at /usr/lib/perl5/5.26.1/TAP/Parser/IteratorFactory.pm line 261.
TAP::Parser::IteratorFactory::detect_source(TAP::Parser::IteratorFactory=HASH(0x5563f4c92c20), TAP::Parser::Source=HASH(0x5563f4c92ab8)) called at /usr/lib/perl5/5.26.1/TAP/Parser/IteratorFactory.pm line 211
TAP::Parser::IteratorFactory::make_iterator(TAP::Parser::IteratorFactory=HASH(0x5563f4c92c20), TAP::Parser::Source=HASH(0x5563f4c92ab8)) called at /usr/lib/perl5/5.26.1/TAP/Parser.pm line 472
TAP::Parser::_initialize(TAP::Parser=HASH(0x5563f4c92818), HASH(0x5563f4a1dff0)) called at /usr/lib/perl5/5.26.1/TAP/Object.pm line 55
TAP::Object::new("TAP::Parser", HASH(0x5563f4a1dff0)) called at /usr/lib/perl5/5.26.1/TAP/Object.pm line 130
TAP::Object::_construct(TAP::Harness=HASH(0x5563f445fe50), "TAP::Parser", HASH(0x5563f4a1dff0)) called at /usr/lib/perl5/5.26.1/TAP/Harness.pm line 852
TAP::Harness::make_parser(TAP::Harness=HASH(0x5563f445fe50), TAP::Parser::Scheduler::Job=HASH(0x5563f4c62df8)) called at /usr/lib/perl5/5.26.1/TAP/Harness.pm line 651
TAP::Harness::_aggregate_single(TAP::Harness=HASH(0x5563f445fe50), TAP::Parser::Aggregator=HASH(0x5563f4900670), TAP::Parser::Scheduler=HASH(0x5563f4c62d98)) called at /usr/lib/perl5/5.26.1/TAP/Harness.pm line 743
TAP::Harness::aggregate_tests(TAP::Harness=HASH(0x5563f445fe50), TAP::Parser::Aggregator=HASH(0x5563f4900670), "17-basetest.t") called at /usr/lib/perl5/5.26.1/TAP/Harness.pm line 558
TAP::Harness::__ANON__() called at /usr/lib/perl5/5.26.1/TAP/Harness.pm line 571
TAP::Harness::runtests(TAP::Harness=HASH(0x5563f445fe50), "17-basetest.t") called at /usr/lib/perl5/5.26.1/App/Prove.pm line 546
App::Prove::_runtests(App::Prove=HASH(0x5563f44524e8), HASH(0x5563f48ee168), "17-basetest.t") called at /usr/lib/perl5/5.26.1/App/Prove.pm line 504
App::Prove::run(App::Prove=HASH(0x5563f44524e8)) called at /usr/bin/prove line 13
make[3]: *** [CMakeFiles/test-perl-testsuite.dir/build.make:74: CMakeFiles/test-perl-testsuite] Error 2
make[2]: *** [CMakeFiles/Makefile2:540: CMakeFiles/test-perl-testsuite.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:547: CMakeFiles/test-perl-testsuite.dir/rule] Error 2
make: *** [Makefile:348: test-perl-testsuite] Error 2
</code></pre>
<a name="Steps-to-reproduce"></a>
<h2 >Steps to reproduce<a href="#Steps-to-reproduce" class="wiki-anchor">¶</a></h2>
<ul>
<li>Navigate to your <em>build folder</em> for os-autoinst (i.e. where you ran <code>cmake</code>)</li>
<li>run <code>make test-perl-testsuite TESTS="17-basetest.t</code>, replacing <code>17-basetest.t</code> with any single test or group of tests contained in the <code>t/</code> directory</li>
</ul>
<a name="Problem"></a>
<h2 >Problem<a href="#Problem" class="wiki-anchor">¶</a></h2>
<p>H1. The problem seems to persist regardless of the test the user tries to run<br>
H2. In the case of multiple tests, after all tests have completed, the error refers to the first test listed by the user in the <code>make test-perl-testsuite TESTS="test1, test2 ... testN"</code> command and exits</p>
<a name="Suggestion"></a>
<h2 >Suggestion<a href="#Suggestion" class="wiki-anchor">¶</a></h2>
<p>Since this problem is unlikely to have existed for long without anyone noticing, it is probably a regression. Locating a commit that caused this behaviour could be a good start.</p>
<a name="Workaround"></a>
<h2 >Workaround<a href="#Workaround" class="wiki-anchor">¶</a></h2>
<p>Running the tests will still produce all expected results, so no special action is needed</p>
openQA Project - action #89221 (Resolved): Statistics about the time it takes developers from QA ...https://progress.opensuse.org/issues/892212021-02-26T15:59:31ZVANASTASIADISvasilios.anastasiadis@suse.com
<p>After discussions with colleagues, bellow are the <strong>yearly</strong> results concerning the median and mean time tickets spend in 'open' state (that is, from the moment they are created until they get closed/resolved).</p>
<p>Some notes:</p>
<ul>
<li>Text parsing was used to filter out the issues related to failing tests. Even though that means the results are not 100% accurate (some tickets concerning failing tests may be left out, and some irrelevant tickets may be included), after manually checking a decent sample of the returned tickets' subjects and talking with test developers, I have concluded that the accuracy is good enough.</li>
<li>Each ticket is counted as belonging to the year it was closed. That means, if a ticket opens in 2017 and closes in 2020, it will be counted as a 2020 ticket with a time being open of 3 years.</li>
<li>Various other results were calculated which are not provided here. If any other results are needed, contact me and I may have them (or easily collect them).</li>
</ul>
<p>That obviously favors previous years, so I used median instead of mean to filter out the extreme outliers.</p>
<a name="RESULTS"></a>
<h2 >RESULTS:<a href="#RESULTS" class="wiki-anchor">¶</a></h2>
<table><thead>
<tr>
<th>YEAR</th>
<th>MEDIAN DAYS OPEN</th>
</tr>
</thead><tbody>
<tr>
<td>2014</td>
<td>39.5</td>
</tr>
<tr>
<td>2015</td>
<td>(No tickets closed in 2015)</td>
</tr>
<tr>
<td>2016</td>
<td>12</td>
</tr>
<tr>
<td>2017</td>
<td>13</td>
</tr>
<tr>
<td>2018</td>
<td>13</td>
</tr>
<tr>
<td>2019</td>
<td>13</td>
</tr>
<tr>
<td>2020</td>
<td>11</td>
</tr>
<tr>
<td>2021</td>
<td>8</td>
</tr>
</tbody></table>
<p>Code used for getting those results resides in <a href="https://gitlab.suse.de/VANASTASIADIS/redminetools" class="external">https://gitlab.suse.de/VANASTASIADIS/redminetools</a> under <code>getFailingPoos</code>. It is just a quick script, super raw and ugly, not following python naming conventions but I still thought I'd put it here for anyone who wants to peek. If you want to point out any things I missed or add anything yourself, feel free to.</p>
openQA Project - action #88507 (Blocked): Create a reports page in SMELT to display not accepted ...https://progress.opensuse.org/issues/885072021-02-09T14:30:23ZVANASTASIADISvasilios.anastasiadis@suse.com
<p>As requested by Vit, a page in smelt where all not accepted requests will be displayed is wanted. The reason for it is to be able to track rejections, regressions and any other negative aspects of our work.</p>
<p>After talking with the Maintsec POs and Vit, it was decided that this page would be better off as a standalone Reports page instead of being an addition to the <code>tested-declined</code> page, in order to avoid confusion.</p>
openQA Project - action #88125 (Resolved): Get feedback and adapt the population scripts for test...https://progress.opensuse.org/issues/881252021-01-21T13:34:04ZVANASTASIADISvasilios.anastasiadis@suse.com
<p>The testreports db and page is implemented, merge request is at <a href="https://gitlab.suse.de/tools/smelt/-/merge_requests/588" class="external">https://gitlab.suse.de/tools/smelt/-/merge_requests/588</a></p>
<p>The correct way to populate this is tricky, and I am discussing with Andreas from coordination about what is the best way to do it. Once decided upon, any changes will be implemented and the request will be merged.</p>