OST UI tests are skipped during check patch for OST repo
Hi all, I've recently refactored some of the UI tests in the OST basic suite and added a new test for integration with Grafana [1]. I pushed my patches to Gerrit, however, I am not able to run them because during the check patch CI job (almost) all UI tests are skipped [2]. How can I make Jenkins to run them? Regards, Lucia 1: https://gerrit.ovirt.org/#/c/ovirt-system-tests/+/112737/ 2: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/14501/....
On 12/21/20 9:08 AM, Lucia Jelinkova wrote:
Hi all,
I've recently refactored some of the UI tests in the OST basic suite and added a new test for integration with Grafana [1]. I pushed my patches to Gerrit, however, I am not able to run them because during the check patch CI job (almost) all UI tests are skipped [2].
How can I make Jenkins to run them? Hi Lucia,
unfortunately we don't have that in u/s CI at the moment. We had to drop all el7 jobs to get rid of all the legacy stuff and complete our move to el8 and py3. In el7 we had docker with its socket exposed to mock, so we could use containers to run the selenium grid. In el8 there is no docker, we have podman. Podman on it's own doesn't work in mock chroot. With CentOS 8.3 there was some hope, since the version of podman provided has an experimental socket support, meaning we could use it the same way like we used docker. I tried it out, but even though the socket itself works, there are limitations on the network implementation side. To have the complete setup working, we need the browsers running inside containers to be able to access engine's http server. This is only possible when using slirp4netns networking backend. Unfortunately with this version of podman there is no way to choose networking backend for pods. For now, my advice would be to try running OST on your own machine. If it has 16GBs of RAM and ~12GBs of free space on /, then you should be good. There's a thread on devel mailing list called "How to set up a (rh)el8 machine for running OST" where you can find instructions on how to prepare your machine for running OST. I'm keeping my eye on the podman situation and will let you know if we have something working. Regards, Marcin
Regards,
Lucia
1: https://gerrit.ovirt.org/#/c/ovirt-system-tests/+/112737/ <https://gerrit.ovirt.org/#/c/ovirt-system-tests/+/112737/> 2: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/14501/... <https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/14501/testReport/basic-suite-master.test-scenarios/test_100_basic_ui_sanity/>.
_______________________________________________ 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/IRJ7Q5VJTKHMXL...
On 21 Dec 2020, at 10:32, Marcin Sobczyk <msobczyk@redhat.com> wrote:
On 12/21/20 9:08 AM, Lucia Jelinkova wrote: Hi all,
I've recently refactored some of the UI tests in the OST basic suite and added a new test for integration with Grafana [1]. I pushed my patches to Gerrit, however, I am not able to run them because during the check patch CI job (almost) all UI tests are skipped [2].
How can I make Jenkins to run them? Hi Lucia,
unfortunately we don't have that in u/s CI at the moment.
We had to drop all el7 jobs to get rid of all the legacy stuff and complete our move to el8 and py3. In el7 we had docker with its socket exposed to mock, so we could use containers to run the selenium grid. In el8 there is no docker, we have podman. Podman on it's own doesn't work in mock chroot. With CentOS 8.3 there was some hope, since the version of podman provided has an experimental socket support, meaning we could use it the same way like we used docker.
I tried it out, but even though the socket itself works, there are limitations on the network implementation side. To have the complete setup working, we need the browsers running inside containers to be able to access engine's http server. This is only possible when using slirp4netns networking backend. Unfortunately with this version of podman there is no way to choose networking backend for pods.
For now, my advice would be to try running OST on your own machine. If it has 16GBs of RAM and ~12GBs of free
8GB RAM is enough for basic suite
space on /, then you should be good. There's a thread on devel mailing list called "How to set up a (rh)el8 machine for running OST" where you can find instructions on how to prepare your machine for running OST.
I'm keeping my eye on the podman situation and will let you know if we have something working.
Keep nagging CI team for mock-less env. Also, downstream manual runs are without mock
Regards, Marcin
Regards,
Lucia
1: https://gerrit.ovirt.org/#/c/ovirt-system-tests/+/112737/ <https://gerrit.ovirt.org/#/c/ovirt-system-tests/+/112737/> 2: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/14501/... <https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/14501/testReport/basic-suite-master.test-scenarios/test_100_basic_ui_sanity/>.
_______________________________________________ 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/IRJ7Q5VJTKHMXL...
_______________________________________________ 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/A6YJJN5KCONHIU...
Thank you Marcin and Michal for your answers. I'll "debug" the tests locally or on downstream CI then. I hope they can be enabled upstream soon too. Regards, Lucia On Mon, Dec 21, 2020 at 1:06 PM Michal Skrivanek < michal.skrivanek@redhat.com> wrote:
On 21 Dec 2020, at 10:32, Marcin Sobczyk <msobczyk@redhat.com> wrote:
On 12/21/20 9:08 AM, Lucia Jelinkova wrote: Hi all,
I've recently refactored some of the UI tests in the OST basic suite and added a new test for integration with Grafana [1]. I pushed my patches to Gerrit, however, I am not able to run them because during the check patch CI job (almost) all UI tests are skipped [2].
How can I make Jenkins to run them? Hi Lucia,
unfortunately we don't have that in u/s CI at the moment.
We had to drop all el7 jobs to get rid of all the legacy stuff and complete our move to el8 and py3. In el7 we had docker with its socket exposed to mock, so we could use containers to run the selenium grid. In el8 there is no docker, we have podman. Podman on it's own doesn't work in mock chroot. With CentOS 8.3 there was some hope, since the version of podman provided has an experimental socket support, meaning we could use it the same way like we used docker.
I tried it out, but even though the socket itself works, there are limitations on the network implementation side. To have the complete setup working, we need the browsers running inside containers to be able to access engine's http server. This is only possible when using slirp4netns networking backend. Unfortunately with this version of podman there is no way to choose networking backend for pods.
For now, my advice would be to try running OST on your own machine. If it has 16GBs of RAM and ~12GBs of free
8GB RAM is enough for basic suite
space on /, then you should be good. There's a thread on devel mailing list called "How to set up a (rh)el8 machine for running OST" where you can find instructions on how to prepare your machine for running OST.
I'm keeping my eye on the podman situation and will let you know if we have something working.
Keep nagging CI team for mock-less env. Also, downstream manual runs are without mock
Regards, Marcin
Regards,
Lucia
1: https://gerrit.ovirt.org/#/c/ovirt-system-tests/+/112737/ <
https://gerrit.ovirt.org/#/c/ovirt-system-tests/+/112737/>
2: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/14501/... < https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/14501/... .
_______________________________________________ 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/IRJ7Q5VJTKHMXL...
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/A6YJJN5KCONHIU...
participants (3)
-
Lucia Jelinkova -
Marcin Sobczyk -
Michal Skrivanek