Thank you Nir, I've tried the tool today and it works nicely. Regards, Lucia On Thu, Jun 25, 2020 at 2:50 PM Nir Soffer <nsoffer@redhat.com> wrote:
On Wed, Jun 24, 2020 at 1:37 PM Lucia Jelinkova <ljelinko@redhat.com> wrote:
Hi all,
If you're running manual OST tests Jenkins job [1] with custom
repository pointing to your ovirt-engine Gerrit check patch job, you most probably notice that the UI tests are failing with one of the following errors:
basic-suite-master.test-scenarios.100_basic_ui_sanity_pytest.test_left_nav[firefox]
basic-suite-master.test-scenarios.100_basic_ui_sanity_pytest.test_virtual_machines[chrome]
This is due to the fact that the normal check patch job does not always
build GWT (first error) or it does not build GWT for both Firefox and Chrome (second error). If you want to test your ovirt-engine patch, please comment "ci build" on the patch, wait for the job to finish and use that job as a custom repository to run tests.
I know that many devs know this "trick" but it might not be so clear for
people not so long on the project.
This is not really a trick, but the only valid way to run system tests.
To avoid such errors people can use the ovirt-ci tool: https://github.com/nirs/ovirt-ci
Running OST is just:
./ovirt-ci system-tests 109794
Nir
If you see any other issue, look into the screenshots or saved html in the exported artifacts. If you think it is a problem with tests, please contact me.
Regards,
Lucia
1: https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests...
_______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/O7GQ6HYFTIFTFB...