Nigel,
Could you give a machine where geo-rep is failing even with bashrc fix to debug ?On Fri, Jan 12, 2018 at 3:54 PM, Amar Tumballi <atumball@xxxxxxxxxx> wrote:
Can we have a separate test case to validate for all the basic necessity for whole test suite to pass? That way the very first run will report an error in the setup and we can fix it faster, instead of waiting for the failure which is a setup issue after 3-4hrs ?-AmarOn Fri, Jan 12, 2018 at 3:47 PM, Atin Mukherjee <amukherj@xxxxxxxxxx> wrote:______________________________On Thu, Jan 11, 2018 at 10:15 AM, Nigel Babu <nigelb@xxxxxxxxxx> wrote:Hello folks,
We may have been a little too quick to blame Meltdown on the Jenkins failures yesterday. In any case, we've open a ticket with our provider and they're looking into the failures. I've looked at the last 90 failures to get a comprehensive number on the failures.
Total Jobs: 90
Failures: 62
Failure Percentage: 68.89%
I've analyzed the individual failures categorized them as well.
slave28.cloud.gluster.org failure: 9
Geo-replication failures: 12
Fops-during-migration.t: 4
Compilation failures: 3
durability-off.t failures: 7
These alone total to 35 failures. The slave28 failures were due to the machine running out of disk space. We had a very large binary archived from an experimental branch build failure. I've cleared that core out and this is now fixed. The geo-replication failures were due to geo-rep tests depending on root's .bashrc having the PATH variable modified. This was not a standard setup and therefore didn't work on many machines. This has now been fixed. The other 3 were transient failures either limited to a particular review or a temporary bustage on master. The majority of the recent failures had more to do with infra than to do with tests.While Nigel tells me that the infra related problems for geo-rep tests are already fixed, I see a similar failure pops up through https://build.gluster.org/job/centos6-regression/8356/consol .e @Kotresh - Could you check if this is something different?
I'm therefore cautiously moving with the assumption that the impact of KPTI patch is minimal so far.
--nigelb
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel _________________
Gluster-infra mailing list
Gluster-infra@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-infra --Amar Tumballi (amarts)
--
Thanks and Regards,
Kotresh H R_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel
