openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842019-03-20T10:50:27ZopenSUSE Project Management Tool
Redmine QA - coordination #49502 (Blocked): [qe-core] Automatic validation test on github PRshttps://progress.opensuse.org/issues/495022019-03-20T10:50:27Zcachencachen@suse.com
<p>Purpose: <br>
-To reduce the unexpected disturbance by other's code change especially on those sharing lib/module<br>
-To make QA developers and code reviewers life much easier</p>
<p>What we have: <br>
-QSF team had an implementation which can manually trigger the expected validation test on OSD, description is in <a href="http://open.qa/docs/#_triggering_tests_based_on_an_any_remote_git_refspec_or_open_github_pull_request" class="external">http://open.qa/docs/#_triggering_tests_based_on_an_any_remote_git_refspec_or_open_github_pull_request</a></p>
<p>What are missing:<br>
-ideally to make it fully automated, it need a review bot integrate to github can automatic monitor the PR status -> trigger/schedule validation tests on OSD or Staging area -> update status to github</p>
<p>The points from coolo:<br>
-easiest to do is in python<br>
-<a href="https://developer.github.com/v3/repos/statuses/" class="external">https://developer.github.com/v3/repos/statuses/</a> is the github api to set a status report and there are python apis for it<br>
-<a href="https://github.com/openSUSE/obs-tools/tree/master/pull_request_package" class="external">https://github.com/openSUSE/obs-tools/tree/master/pull_request_package</a> is a ruby bot that obs team maintains to set a status in their PRs if the package builds<br>
-so you would poll the pull requests if the status is set - and if it isn't, schedule a set of openQA tests the way okurz mentioned, wait for them to finish and update the github status</p>
<p>What we need:<br>
-contributor who is interested on python and github bot for automation :)</p>
openQA Tests - action #38765 (Resolved): [openqa][ipmi] "logs_from_installation_system" step fail...https://progress.opensuse.org/issues/387652018-07-24T05:49:38Zcachencachen@suse.com
<p><a href="https://openqa.nue.suse.com/tests/1853694#step/logs_from_installation_system/11" class="external">https://openqa.nue.suse.com/tests/1853694#step/logs_from_installation_system/11</a></p>
<p>Similar failure happens quite often on the servers, which has multi hard disks.</p>
<p>diff --git a/lib/ipmi_backend_utils.pm b/lib/ipmi_backend_utils.pm<br>
index 18830256..7a78c963 100644<br>
--- a/lib/ipmi_backend_utils.pm<br>
+++ b/lib/ipmi_backend_utils.pm<br>
@@ -146,7 +146,7 @@ sub umount_installation_disk {<br>
}</p>
<p>sub get_installation_partition {</p>
<ul>
<li> my $partition = script_output("fdisk -l | grep \"<sup>\/dev\/sda.*\*\"</sup> | cut -d ' ' -f 1");</li>
<li> my $partition = script_output("fdisk -l | grep \"<sup>\/dev\/sd.*\*\"</sup> | cut -d ' ' -f 1");
return $partition;
}</li>
</ul>
<p>This may fix the issue, but I have test in openQA.</p>
openQA Tests - action #18124 (Resolved): [userspace][ppc64le]sles12_qa_userspace_nfs/nfsv4 random...https://progress.opensuse.org/issues/181242017-03-29T10:15:29Zcachencachen@suse.com
<p>usermapping_norootsquash and usermapping_allsquash testcases sometimes random fail only in openQA vm environment, but pass in real host.</p>
<p><a href="https://openqa.suse.de/tests/833278#previous" class="external">https://openqa.suse.de/tests/833278#previous</a></p>