<div dir="ltr">After the recent merge of testing install of ovirt-cockpit-dashboard to 3.6,<div>the 4.0 tests failed also. [1]</div><div><br></div><div>And then I found out that some of the 4.0 tests are linked to 3.6 still, is this intentional?</div><div>Should we now create a new separate 4.0 test or change the link to master?</div><div><br></div><div><div>lrwxrwxrwx. 1 eedri eedri 64 Jun 22 00:12 001_initialize_engine.py -> ../../basic_suite_master/test-scenarios/001_initialize_engine.py</div><div>lrwxrwxrwx. 1 eedri eedri 53 Jun 22 00:12 002_bootstrap.py -> ../../basic_suite_3.6/test-scenarios/002_bootstrap.py</div><div>lrwxrwxrwx. 1 eedri eedri 56 Jun 22 00:12 004_basic_sanity.py -> ../../basic_suite_3.6/test-scenarios/004_basic_sanity.py</div></div><div><br></div><div><br></div><div><br></div><div>[1] <a href="http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/72/console">http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/72/console</a><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Eyal Edri<br>Associate Manager</div><div>RHEV DevOps<br>EMEA ENG Virtualization R&D<br>Red Hat Israel<br><br>phone: +972-9-7692018<br>irc: eedri (on #tlv #rhev-dev #rhev-integ)</div></div></div></div></div>
</div></div>