openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842016-10-19T04:16:46ZopenSUSE Project Management Tool
Redmine openQA Project - action #14306 (Resolved): It will resolve big trouble on multi-machine job if we...https://progress.opensuse.org/issues/143062016-10-19T04:16:46Zjerrytangjtang@suse.com
<p>Here is the issue.<br>
1.we perform a testsuite job require machines.</p>
<ol>
<li>machine 1 set_var(TARGET_VAR_1,"test").use mutex_lock to sync with machine2.</li>
<li>machine use get get_job_info([machine's job_id) to get all variable and query the 'TARGET_VAR_1' .</li>
</ol>
<p>the result is : we can NOT get the value.</p>
<p>I assume it not supported yet. so I open this request hope this can be implemented.</p>
<p>because once this feature done ,it will easy to communicate for the mutil-machine job, this will significant reduce the workaround code.</p>
openQA Project - action #13972 (Rejected): openqa scheduler can not schedule the multi-machine jo...https://progress.opensuse.org/issues/139722016-09-29T08:00:38Zjerrytangjtang@suse.com
<p>I have 2 phy-machine with ipmi .<br>
I need assign 2 ipmi-worker to 2 test-suites(jobs) with parallel dependence .</p>
<p>1 Setup 2 ipmi-workers with different WORKER_CLASS ,(specify the ipmi to the phy-machine)<br>
2 Add 2 test(job) to same group with different "WORKER_CLASS";</p>
<p>When i trigger the job with parallel, the dependence job can not schedule.</p>
<p>After use same "WORKER_CLASS" , this issue is gone</p>
openQA Project - action #11372 (Resolved): ikvm: no message action for 0x80/128 unsupported messa...https://progress.opensuse.org/issues/113722016-04-01T10:39:48Zjerrytangjtang@suse.com
<p>I'm just doing the test on supermicro machine by ikvm.<br>
after setup the impi ENV , I got the error : <br>
I print the message_type , is 128 .</p>
<p><a href="http://147.2.212.197/tests/254/file/autoinst-log.txt">http://147.2.212.197/tests/254/file/autoinst-log.txt</a></p>
<p>/usr/lib/os-autoinst/consoles/vnc_base.pm:49:{<br>
'ikvm' => 1,<br>
'username' => 'ADMIN',<br>
'password' => 'ADMIN',<br>
'port' => 5900,<br>
'hostname' => '147.2.208.125'<br>
}<br>
Session info: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <br>
Security Result: 0<br>
IKVM specifics: 1129866464 1 1 1 1<br>
IKVM Session Message: 1 1 1129866464 ADMIN <br>
09:30:28.6266 capture loop failed Can't close(GLOB(0x625f7e8)) filehandle: 'No child processes' at /usr/lib/os-autoinst/backend/baseclass.pm line 267</p>
<p>received magic close<br>
discarding 20 bytes for message 4<br>
DIE 128 unsupported message type received at /usr/lib/os-autoinst/consoles/VNC.pm line 786.</p>
<p>at /usr/lib/os-autoinst/backend/baseclass.pm line 73 thread 1.<br>
backend::baseclass::die_handler('128 unsupported message type received at /usr/lib/os-autoinst...') called at /usr/lib/os-autoinst/consoles/VNC.pm line 786 thread 1<br>
consoles::VNC::_receive_message('consoles::VNC=HASH(0x7efde0112220)') called at /usr/lib/os-autoinst/consoles/VNC.pm line 740 thread 1<br>
consoles::VNC::update_framebuffer('consoles::VNC=HASH(0x7efde0112220)') called at /usr/lib/os-autoinst/consoles/vnc_base.pm line 80 thread 1<br>
consoles::vnc_base::request_screen_update('consoles::vnc_base=HASH(0x625f8c0)', undef) called at /usr/lib/os-autoinst/backend/baseclass.pm line 522 thread 1<br>
backend::baseclass::bouncer('backend::ipmi=HASH(0x5e91f88)', 'request_screen_update', undef) called at /usr/lib/os-autoinst/backend/baseclass.pm line 505 thread 1<br>
backend::baseclass::request_screen_update('backend::ipmi=HASH(0x5e91f88)') called at /usr/lib/os-autoinst/backend/baseclass.pm line 180 thread 1<br>
eval {...} called at /usr/lib/os-autoinst/backend/baseclass.pm line 164 thread 1<br>
backend::baseclass::run_capture_loop('backend::ipmi=HASH(0x5e91f88)', 'IO::Select=ARRAY(0x55582c8)') called at /usr/lib/os-autoinst/backend/baseclass.pm line 113 thread 1<br>
backend::baseclass::run('backend::ipmi=HASH(0x5e91f88)', 13, 16) called at /usr/lib/os-autoinst/backend/driver.pm line 82 thread 1<br>
backend::driver::_run('backend::ipmi=HASH(0x5e91f88)', 13, 16) called at /usr/lib/os-autoinst/backend/driver.pm line 69 thread 1<br>
eval {...} called at /usr/lib/os-autoinst/backend/driver.pm line 69 thread 1<br>
09:30:29.1834 IPMI cmd : ipmitool -H 147.2.208.125 -U ADMIN -P ADMIN chassis power off <br>
IPMI stdout: Chassis Power Control: Down/Off</p>
openQA Project - action #10604 (Resolved): mutex lock looks does not work https://progress.opensuse.org/issues/106042016-02-05T08:28:14Zjerrytangjtang@suse.com
<p>I create 2 parallel job (jerry,jerry1):</p>
<a name="for-jerry1-parent"></a>
<h1 >for jerry1 (parent):<a href="#for-jerry1-parent" class="wiki-anchor">¶</a></h1>
<p>sub run() {<br>
check_screen "jerry_wait11", 300;<br>
mutex_create('xxx');<br>
sleep 20;<br>
}</p>
<a name="1"></a>
<h1 >1;<a href="#1" class="wiki-anchor">¶</a></h1>
<a name="for-jerry-child"></a>
<h1 >for jerry (child):<a href="#for-jerry-child" class="wiki-anchor">¶</a></h1>
<p>#!/usr/bin/perl -w <br>
use strict;<br>
use base "basetest";<br>
use testapi;<br>
use lockapi;</p>
<p>sub run() {<br>
mutex_unlock('xxx');<br>
sleep 20;<br>
}</p>
<a name="1-2"></a>
<h1 >1;<a href="#1-2" class="wiki-anchor">¶</a></h1>
<p>two job in same test group.</p>
<p>I run this jobs , it was started in parallel. but test mutex does work ,</p>
<p>mutex_unlock won't in block. </p>
<p>and I wonder how does block looks like : "mutex lock 'xxx' unavailable, sleeping 5s" ?</p>
<p>if like this. I think it is from mutex_lock function in lockapi . (which means mutex_unlock won't block right?)</p>