On Wed, Aug 10, 2016 at 3:41 PM, Irit Goihman <firstname.lastname@example.org> wrote:
> jobs vdsm_master_build-artifacts-el7-ppc64le and vdsm_master_check-merged-el7-x86_64
> keep failing. They were created recently and should be removed.
The ppc64le should be fixed, not removed.
We want ppc64le builds now that we have ppc64le slaves.
The check-merged for el7 is your call, fine for me if you want to remove.
Just weird since el7 is our main target.
> Irit Goihman
> Software Engineer
> Red Hat Israel Ltd.
> Infra mailing list
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
Until recently el7 check merged job didn't exist and we had a job only for fc23 that moved to fc24.
check-merged job is using a lago setup with fc24 vm and checks only fc24 packages.
We are planning to add el7 vm that will run tests on el7 packages as well.
On Wed, Aug 10, 2016 at 8:06 PM, eyal edri [Administrator] (oVirt JIRA) <
This is related to check-patch, check-path and build-artifacts should run
over all platforms. as many as possible.. Check-merged is a script to test
our functional flows - we run lago, and fedora vm inside that runs vdsmd
and some functional test. currently lago vm is fedora based, so vdsm rpms
to be installed should be built over fedora, therefore the jenkins vm is
fedora as well.
We don't run the functional tests over centos\el7 vm currently, so running
it on jenkins el7 vm is redundant and won't work (the rpms won't fit for
the lago vm inside, and it will only test lago run over el7).
That's why we ask to run check-merged CI only over f24 (as it used to be
not so long ago)
I understand you want to remove the el7 job for master, the question is why?
If we want to fix it, I suggest to keep it or at least disable it, otherwise we'll just forget about it.
if its only check-merged then it doesn't give -1 on patches and its not blocking patches.
also, if there is something the infra team can do to help with fixing el7 please let us know
removed master el7 check-merged from yaml for now.