action #44465
openWebui shows one test module but worker starts a different one
0%
Description
I have two versions of one test module: one in /var/lib/openqa and one in /openqa-share. The latter is an NFS mount and specified as SHARE_DIRECTORY in my workers.ini (attached). The webui displays the one from /openqa-share [0], but a different on is executed [1]. The module in /var/lib/openqa (attached) includes "grep 127.0.0.1 /etc/hosts" while that line is different in the /openqa-share one. I edited the test case in /openqa-share before starting a new run.
[0] - http://agraul-vm.qa.suse.de/tests/18/modules/yast2_hostnames/steps/1/src
[1] - http://agraul-vm.qa.suse.de/tests/18#step/yast2_hostnames/16
Files
Updated by mkittler about 6 years ago
Right observation. In fact, the web UI always shows the test code as it is available right now under $OPENQA_BASEDIR/openqa/share/tests. So the web UI also shows different code compared to what was actually executed in the case when the test code has been updated since the test was executed.
Since the worker and the web UI might not run on the same machine we can't simply use the path from the workers.ini to fix your use case. I suppose the worker would need to upload the test code like other artifacts to implement this.
Updated by agraul about 6 years ago
But shouldn't the test in SHARE_DIRECTORY be executed when that is defined in workers.ini? In my case the test from SHARE_DIRECTORY is shown in the webui, but a different one is executed (the one in /var/lib/openqa). I edited the one in /var/lib/openqa and had another run: http://agraul-vm.qa.suse.de/tests/19#step/yast2_hostnames/15.