Re: Migration of the builders to Fedora 30

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On Thu, Jul 4, 2019 at 9:55 PM Amar Tumballi Suryanarayan <atumball@xxxxxxxxxx> wrote:


On Thu, Jul 4, 2019 at 9:37 PM Michael Scherer <mscherer@xxxxxxxxxx> wrote:
Hi,

I have upgraded for testing some of the builder to F30 (because F28 is
EOL and people did request newer version of stuff), and I was a bit
surprised to see the result of the test of the jobs.

So we have 10 jobs that run on those builders.

5 jobs run without trouble:
- python-lint
- clang-scan
- clang-format
- 32-bit-build-smoke
- bugs-summary

1 is disabled, tsan. I didn't try to run it.

4 fails:
- python-compliance 

OK to run, but skip voting, so we can eventually (soonish) fix this.
 
- fedora-smoke

Ideally we should soon fix it. Effort is ON. We have a bug for this: https://bugzilla.redhat.com/show_bug.cgi?id=1693385#c5 

Can we re-run this on latest master? I think we are ready for  fedora-smoke on fedora30 on latest master. 

 
- gluster-csi-containers
- glusterd2-containers


OK to drop for now.
 
The job python-compliance fail like this:
https://build.gluster.org/job/python-compliance/5813/

The fedora-smoke job, who is building on newer fedora (so newer gcc),
is failling too:
https://build.gluster.org/job/fedora-smos some new vol option that ought to be set?ke/6753/console

Gluster-csi-containers is having trouble to run
https://build.gluster.org/job/gluster-csi-containers/304/console
https://bugzilla.redhat.com/show_bug.cgi?id=1693385#c5
but before, it did fail with "out of space":
https://build.gluster.org/job/gluster-csi-containers/303/console

and it also fail (well, should fail) with this:
16:51:07 make: *** No targets specified and no makefile found.  Stop.

which is indeed not present in the git repo, so this seems like the job is unmaintained.


The last one to fail is glusterd2-containers:

https://build.gluster.org/job/glusterd2-containers/323/console

This one is fun, because it fail, but appear as ok on jenkins. It fail
because of some ansible issue, due to newer Fedora.

So, since we need to switch, here is what I would recommend:
- switch the working job to F30
- wait 2 weeks, and switch fedora-smoke and python-compliance to F30. This will force someone to fix the problem.
- drop the non fixed containers jobs, unless someone fix them, in 1 month.

Looks like a good plan. 
 

--
Michael Scherer
Sysadmin, Community Infrastructure



_______________________________________________

Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/836554017

NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/486278655

Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-devel



--
Amar Tumballi (amarts)


--
Amar Tumballi (amarts)
_______________________________________________

Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/836554017

NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/486278655

Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-devel


[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux