stopping the hunt for when this last succeeded :) )
Let's know if anyone is taking a peek at the cores.
Thanks,
Shyam
On 03/04/2016 07:40 AM, Krutika Dhananjay wrote:
Could someone from tiering dev team please take a look?
https://build.gluster.org/job/rackspace-regression-2GB-triggered/18793
On 08/16/2016 09:03 PM, Nigel Babu wrote:
Hello folks,
For the last few weeks, Poornima has been sending in a report of failures over
the last week. I've been thinking of how to use automation to make that report
better. One of the ideas was to use Jenkins to send the email. It seemed like
we
noted, moving this to the respective lists, to get
it on record and proceed with the branch creation.
Thanks,
Shyam
# Request for special FB development branch against 3.8
FB wants to move to release 3.8 and have quite a few patches that they
need to upstream and port into the 3.8 branch for them
On 03/10/2017 02:45 AM, Xavier Hernandez wrote:
Hi,
I've posted a patch [1] to fix a memory leak in locks xlator. The fix
seems quite straightforward, however I've seen a deadlock in the centos
regression twice [2] [3] on the locks_revocation.t test, causing the
test to timeout and be aborted.
to branches in
glusterfs repository
NOTE: This is still under discussion and NEEDINFO on me, but just noting
it here for completeness
The above is P5 as we can live without it (as we have been till now) for
some more time.
Thanks,
Shyam
___
Gluster
expectation was that users would
provide details about the exact version in the bug description. Do we want
to follow a similar process for 3.10?
Thanks Vijay!
May be this is why Shyam hasn't created 3.10.1 version already? If so,
I will not send this request.
We do not add minor version (as discuss
On 12/20/2017 04:30 AM, Nigel Babu wrote:
> Hello folks,
>
> We've been using Centos 6 for our regressions for a long time. I believe
> it's time that we moved to Centos 7. It's causing us minor issues. For
> example, tests run fine on the regression boxes but don't work on local
> machines or
d from
run-tests.sh (when there are retries) then the logs will be archived. We
do not call out a run as a failure in case there were retries, hence no
logs.
I will add this today to the WIP testing patchset.
>
>
> On Sat, Aug 11, 2018 at 9:40 AM Ravishankar N <mailto:ravishan...@redhat
