On Thu, Oct 22, 2020, 13:34 Vojtech Juranek <vjuranek(a)redhat.com> wrote:
On čtvrtek 22. října 2020 11:48:15 CEST Ales Musil wrote:
> On Thu, Oct 22, 2020 at 11:34 AM Vojtech Juranek <vjuranek(a)redhat.com>
> > Hi,
> > some network tests fail on Travis, see e.g. .
> > Could someone from network team take a look?
> > My guess is it's caused by commit 3ec1ad9a9f38 , but I'm not sure.
> > Thanks
> > Vojta
> >  https://travis-ci.org/github/oVirt/vdsm/jobs/737665066
> > 
> > 9f6 _______________________________________________
> > Devel mailing list -- devel(a)ovirt.org
> > To unsubscribe send an email to devel-leave(a)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:
> > P6IOYP32JP5ZHO4RDZ4M/
> the  should fix it. But I am not sure how to test it.
you need to rebuild containers with this change and push it into quay.io
some other docker repository), change the container in .travis.yml and run
test on Travis.
I'm trying to verify it, but upload speed of my link is pretty slow (to
centors container into quay), so it will take some time
An easier way is to build the image locally, start the container in the
we do in travis, and run the network tests in the container.
Since the container is privileged, running it inside a vm is safer.
Another way is to create a new image in quay, connected to your private
vdsm fork on github, and build the image in quay.io. Then change
to use your qauy.io image for testing.
All ways require a lot of time and effort, this is the world of containers
>  https://gerrit.ovirt.org/c/111851/
Devel mailing list -- devel(a)ovirt.org
To unsubscribe send an email to devel-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: