There is a CI issue that's ongoing. There are several problems, most of
them are what Poornima reported last night.
1) Some builds are failing for what looks like infra reasons. This will
need looking into.
2) The Jenkins <-> Gerrit reporting has gone whacky for some reason. If you
see a failure p
On 06/06/2016 06:43 PM, Nigel Babu wrote:
Hello folks,
Here's a postmortem for the Gerrit migration issues
# Timeline of Events
May 25 - Test migration to PostgreSQL
May 27 - Migration to PostgreSQL on production
May 30 - Staging with Gerrit 2.12.2 available for testing
Jun 01 - Gerrit upgrad
Hello folks,
Here's a postmortem for the Gerrit migration issues
# Timeline of Events
May 25 - Test migration to PostgreSQL
May 27 - Migration to PostgreSQL on production
May 30 - Staging with Gerrit 2.12.2 available for testing
Jun 01 - Gerrit upgrade complete ( 0310)
Jun 01 - First notification
On Mon, Jun 06, 2016 at 09:59:02PM +0530, Nigel Babu wrote:
> On Mon, Jun 6, 2016 at 12:56 PM, Poornima Gurusiddaiah
> wrote:
>
> > Hi,
> >
> > There are multiple issues that we saw with regressions lately:
> >
> > 1. On certain slaves the regression fails during build and i see those on
> > slav
This [1] run failed, and I wanted access the logs as posted at [2].
Clicking the link [2] gives an "403 Forbidden" error.
I am logged into Jenkins (if that matters).
Looks like the /exports/logs is not exported on slave1?
Can someone look into it?
Thanks,
Shyam
[1]
https://build.gluster.org
On Mon, Jun 6, 2016 at 12:56 PM, Poornima Gurusiddaiah
wrote:
> Hi,
>
> There are multiple issues that we saw with regressions lately:
>
> 1. On certain slaves the regression fails during build and i see those on
> slave26.cloud.gluster.org, slave25.cloud.gluster.org and may be others
> also.
>
Hi,
There are multiple issues that we saw with regressions lately:
1. On certain slaves the regression fails during build and i see those on
slave26.cloud.gluster.org, slave25.cloud.gluster.org and may be others also.
Eg:
https://build.gluster.org/job/rackspace-regression-2GB-triggered/21422
On Mon, 2016-06-06 at 06:07 -0400, Kaleb KEITHLEY wrote:
> On 06/06/2016 04:48 AM, Anoop C S wrote:
> >
> >
> > From my analysis this happens due to the use of old automake
> > version(v1.11.1) while preparing the release tar ball. Starting
> > from
> > v1.11.2[2] automake has begun to accept emp
On 06/06/2016 04:48 AM, Anoop C S wrote:
>
> From my analysis this happens due to the use of old automake
> version(v1.11.1) while preparing the release tar ball. Starting from
> v1.11.2[2] automake has begun to accept empty arguments to --destdir
> option for auto generated py-compile script for
Hi,
Bump. This request kinda got lost.
Reviewers currently have to rely on running the unit and functional
tests on their machines. A jenkins account will allow me to set CI
jobs for the same. I've already got the machines (gluster-swift-el7-1,
gluster-swift-f22-1) reserved which has been idle fo
Hi all,
Few weeks before a community user reported to gluster-users ML[1] that
he/she encountered the following error while trying to do make install
from glusterfs sources(v3.7.11):
> Making install in glupy
> /usr/bin/mkdir -p '/usr/lib/python2.7/site-packages/gluster/glupy'
> /usr/bin/instal
11 matches
Mail list logo
