Re: [Gluster-devel] [Gluster-infra] Nightly Gerrit start/stop backup job now on review.gluster.org
On 27/09/2014, at 10:49 AM, Niels de Vos wrote: > On Fri, Sep 26, 2014 at 10:32:49PM +0100, Justin Clift wrote: >> There's now a nightly cronjob to stop Gerrit (on review.gluster.org), backup >> Gerrit to another host, and start it up again. > > What time + timezone is 'nightly'? 03:15 UTC. It should only be offline for under a minute (in general), so I'm hoping it has no real noticeable impact. :) > Thanks for taking care of this, No worries. This approach seems like the only way to get a consistent back from Gerrit. "git-daemon" is installed on review.gluster.org too, which needs backing up as well. Haven't yet begun to attack that, but will on Monday. Once that's done, I think all of the services on review.gluster.org will be getting backed up. At that point we can start looking at upgrading Gerrit / migrating it to Rackspace, etc. + Justin > Niels -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] CentOS 7: Gluster Test Framework testcases failure
Testcase tests/bugs/bug-913555.t does not show the peers and please find
the details at http://ur1.ca/i8ybk (http://fpaste.org/136968/)
On Sat, Sep 27, 2014 at 3:26 PM, Kiran Patil wrote:
> Now on XFS, the Test Summary Report is same as running on ZFS except test
> case bug-953887.t failure.
>
> Test case tests/bugs/bug-953887.t expects force at end of line, TEST
> gluster volume add-brick $V0 $H0:$B0/${V0}{2,3} and it passed once force is
> substituted at the end of the line.
>
> Test case tests/bugs/bug-767095.t failed due to path issue and now it no
> more fails.
>
> So the failures are no more specific to on disk filesystems such as ZFS
> and XFS but glusterfs.
>
> Thanks,
> Kiran.
>
> On Sat, Sep 27, 2014 at 1:30 PM, Kiran Patil
> wrote:
>
>> I ran each testcases with DEBUG=1 and pasted at http://ur1.ca/i8xay (
>> http://fpaste.org/136940/)
>>
>> This time I ran the testcases by keeping default paths and now
>> tests/bugs/bug-861542.t passes
>>
>> Need to create /var/run/gluster directory on reboot
>>
>> Test Setup:
>> -
>> CentOS 7 : 3.10.0-123.8.1.el7.x86_64
>>
>> gluster --version : glusterfs 3.4.5 built on Jul 24 2014 19:14:13
>>
>> Zfs : zfs-0.6.3
>>
>> glusterfs testcases version :
>> git branch : * (detached from v3.4.5)
>>
>>
>> Test Summary Report
>> ---
>> ./tests/bugs/bug-802417.t (Wstat: 0 Tests: 39
>> Failed: 2)
>> Failed tests: 28, 31
>> ./tests/bugs/bug-821056.t (Wstat: 0 Tests: 21
>> Failed: 1)
>> Failed test: 15
>> ./tests/bugs/bug-908146.t (Wstat: 0 Tests: 10
>> Failed: 2)
>> Failed tests: 8-9
>> ./tests/bugs/bug-913555.t (Wstat: 0 Tests: 11
>> Failed: 4)
>> Failed tests: 4-6, 9
>> ./tests/bugs/bug-948686.t (Wstat: 0 Tests: 19
>> Failed: 8)
>> Failed tests: 5-7, 9, 11, 13-15
>> ./tests/bugs/bug-948729/bug-948729-force.t (Wstat: 0 Tests: 35
>> Failed: 6)
>> Failed tests: 29-31, 33-35
>> ./tests/bugs/bug-948729/bug-948729-mode-script.t (Wstat: 0 Tests: 35
>> Failed: 6)
>> Failed tests: 29-31, 33-35
>> ./tests/bugs/bug-948729/bug-948729.t(Wstat: 0 Tests: 23
>> Failed: 2)
>> Failed tests: 19, 23
>> Files=123, Tests=2019, 4834 wallclock secs ( 1.62 usr 0.25 sys + 258.83
>> cusr 201.05 csys = 461.75 CPU)
>> Result: FAIL
>>
>> Thanks,
>> Kiran.
>>
>> On Fri, Sep 26, 2014 at 9:32 PM, Lalatendu Mohanty
>> wrote:
>>
>>> On 09/26/2014 02:59 AM, Justin Clift wrote:
>>>
On 25/09/2014, at 9:28 PM, Lalatendu Mohanty wrote:
> Have we published somewhere which distributions or OS versions we are
> running regression tests ? if not lets compile it and publish as this will
> help community to understand which os distributions are part of the
> regression testing.
>
The best we have so far is probably this:
http://www.gluster.org/community/documentation/index.
php/Using_the_Gluster_Test_Framework
Do we have plans to run regression on a variety of distributions? Not
> sure how difficult or complex it is to maintain.
>
The primary OS at the moment is CentOS 6.x (mainly due to it
being the primary OS for GlusterFS I think).
Manu and Harsha have been going through the regression tests
recently, making them more cross platform in order to run on
the BSDs.
This effort has also highlighted some interesting Linux
specific behaviour in the main GlusterFS code base, and led
to fixes there.
In short, we're all for running the regression tests on as
many distributions as possible. If Community members want
to put VM's or something online (medium-long term), I'd be
happy to hook our Jenkins infrastructure up to them to
automatically run tests on them.
Is that kind of what you're asking? :)
>>>
>>> Yup, I will try to get a CentOS 7 instance for running regression tests
>>> :)
>>>
>>> -Lala
>>>
>>
>>
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] CentOS 7: Gluster Test Framework testcases failure
Now on XFS, the Test Summary Report is same as running on ZFS except test
case bug-953887.t failure.
Test case tests/bugs/bug-953887.t expects force at end of line, TEST
gluster volume add-brick $V0 $H0:$B0/${V0}{2,3} and it passed once force is
substituted at the end of the line.
Test case tests/bugs/bug-767095.t failed due to path issue and now it no
more fails.
So the failures are no more specific to on disk filesystems such as ZFS and
XFS but glusterfs.
Thanks,
Kiran.
On Sat, Sep 27, 2014 at 1:30 PM, Kiran Patil wrote:
> I ran each testcases with DEBUG=1 and pasted at http://ur1.ca/i8xay (
> http://fpaste.org/136940/)
>
> This time I ran the testcases by keeping default paths and now
> tests/bugs/bug-861542.t passes
>
> Need to create /var/run/gluster directory on reboot
>
> Test Setup:
> -
> CentOS 7 : 3.10.0-123.8.1.el7.x86_64
>
> gluster --version : glusterfs 3.4.5 built on Jul 24 2014 19:14:13
>
> Zfs : zfs-0.6.3
>
> glusterfs testcases version :
> git branch : * (detached from v3.4.5)
>
>
> Test Summary Report
> ---
> ./tests/bugs/bug-802417.t (Wstat: 0 Tests: 39
> Failed: 2)
> Failed tests: 28, 31
> ./tests/bugs/bug-821056.t (Wstat: 0 Tests: 21
> Failed: 1)
> Failed test: 15
> ./tests/bugs/bug-908146.t (Wstat: 0 Tests: 10
> Failed: 2)
> Failed tests: 8-9
> ./tests/bugs/bug-913555.t (Wstat: 0 Tests: 11
> Failed: 4)
> Failed tests: 4-6, 9
> ./tests/bugs/bug-948686.t (Wstat: 0 Tests: 19
> Failed: 8)
> Failed tests: 5-7, 9, 11, 13-15
> ./tests/bugs/bug-948729/bug-948729-force.t (Wstat: 0 Tests: 35
> Failed: 6)
> Failed tests: 29-31, 33-35
> ./tests/bugs/bug-948729/bug-948729-mode-script.t (Wstat: 0 Tests: 35
> Failed: 6)
> Failed tests: 29-31, 33-35
> ./tests/bugs/bug-948729/bug-948729.t(Wstat: 0 Tests: 23
> Failed: 2)
> Failed tests: 19, 23
> Files=123, Tests=2019, 4834 wallclock secs ( 1.62 usr 0.25 sys + 258.83
> cusr 201.05 csys = 461.75 CPU)
> Result: FAIL
>
> Thanks,
> Kiran.
>
> On Fri, Sep 26, 2014 at 9:32 PM, Lalatendu Mohanty
> wrote:
>
>> On 09/26/2014 02:59 AM, Justin Clift wrote:
>>
>>> On 25/09/2014, at 9:28 PM, Lalatendu Mohanty wrote:
>>>
>>>
Have we published somewhere which distributions or OS versions we are
running regression tests ? if not lets compile it and publish as this will
help community to understand which os distributions are part of the
regression testing.
>>> The best we have so far is probably this:
>>>
>>>http://www.gluster.org/community/documentation/index.
>>> php/Using_the_Gluster_Test_Framework
>>>
>>>
>>> Do we have plans to run regression on a variety of distributions? Not
sure how difficult or complex it is to maintain.
>>> The primary OS at the moment is CentOS 6.x (mainly due to it
>>> being the primary OS for GlusterFS I think).
>>>
>>> Manu and Harsha have been going through the regression tests
>>> recently, making them more cross platform in order to run on
>>> the BSDs.
>>>
>>> This effort has also highlighted some interesting Linux
>>> specific behaviour in the main GlusterFS code base, and led
>>> to fixes there.
>>>
>>> In short, we're all for running the regression tests on as
>>> many distributions as possible. If Community members want
>>> to put VM's or something online (medium-long term), I'd be
>>> happy to hook our Jenkins infrastructure up to them to
>>> automatically run tests on them.
>>>
>>> Is that kind of what you're asking? :)
>>>
>>
>> Yup, I will try to get a CentOS 7 instance for running regression tests :)
>>
>> -Lala
>>
>
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-infra] Nightly Gerrit start/stop backup job now on review.gluster.org
On Fri, Sep 26, 2014 at 10:32:49PM +0100, Justin Clift wrote: > Hi all, > > There's now a nightly cronjob to stop Gerrit (on review.gluster.org), backup > Gerrit to another host, and start it up again. What time + timezone is 'nightly'? Thanks for taking care of this, Niels > > (whilst working on it, I noticed some wrong file ownership/permissions again, > so fixed those too) > > If you experience any weirdness with the review.gluster.org server, please let > me know. :) > > Regards and best wishes, > > Justin Clift > > -- > GlusterFS - http://www.gluster.org > > An open source, distributed file system scaling to several > petabytes, and handling thousands of clients. > > My personal twitter: twitter.com/realjustinclift > > ___ > Gluster-infra mailing list > gluster-in...@gluster.org > http://www.gluster.org/mailman/listinfo/gluster-infra ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] Reviews needed before a glusterfs-3.5.3 beta can be released
Hi all,
I'd like to point out that there are reviews needed before I will merge
changes in the release-3.5 branch. Many bugs that have been proposed as
a blocker [1] for gluserfs-3.5.3 have patches posted. Bugs that are in
the POST state, should have links to the review request, please have a
look:
$ bugzilla query --blocked=glusterfs-3.5.3 --bug_status=NEW,ASSIGNED,POST
--outputformat='%{id} %{status}: %{summary}'
1092037 POST: Issues reported by Cppcheck static analysis tool
1113050 ASSIGNED: Transient failures immediately after add-brick to a mounted
volume
1117888 NEW: Problem when enabling quota : Could not start quota auxiliary
mount
1129541 POST: [DHT:REBALANCE]: Rebalance failures are seen with error message
" remote operation failed: File exists"
1134050 NEW: Glfs_fini() not freeing the resources
1138922 POST: DHT + rebalance : rebalance process crashed + data loss + few
Directories are present on sub-volumes but not visible on mount point + lookup
is not healing directories
1139103 POST: DHT + Snapshot :- If snapshot is taken when Directory is
created only on hashed sub-vol; On restoring that snapshot Directory is not
listed on mount point and lookup on parent is not healing
1139170 POST: DHT :- rm -rf is not removing stale link file and because of
that unable to create file having same name as stale link file
1140338 POST: rebalance is not resulting in the hash layout changes being
available to nfs client
1140348 POST: Renaming file while rebalance is in progress causes data loss
1140549 POST: DHT: Rebalance process crash after add-brick and `rebalance
start' operation
1140556 POST: Core: client crash while doing rename operations on the mount
The few bugs that are in NEW or ASSIGNED state still need some work. If
there is no progress before next Wednesday, those bugs will get moved to
the glusterfs-3.5.4 tracker [2].
Currently, there are several changes pending review for 3.5. You can
help out by reviewing changes that get listed by a Gerrit query,
conveniently saved with a shorturl [3].
Thanks for your help,
Niels
1.
https://bugzilla.redhat.com/showdependencytree.cgi?maxdepth=1&hide_resolved=1&id=glusterfs-3.5.3
2. https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.5.4
3. http://goo.gl/1riaVk
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] CentOS 7: Gluster Test Framework testcases failure
I ran each testcases with DEBUG=1 and pasted at http://ur1.ca/i8xay ( http://fpaste.org/136940/) This time I ran the testcases by keeping default paths and now tests/bugs/bug-861542.t passes Need to create /var/run/gluster directory on reboot Test Setup: - CentOS 7 : 3.10.0-123.8.1.el7.x86_64 gluster --version : glusterfs 3.4.5 built on Jul 24 2014 19:14:13 Zfs : zfs-0.6.3 glusterfs testcases version : git branch : * (detached from v3.4.5) Test Summary Report --- ./tests/bugs/bug-802417.t (Wstat: 0 Tests: 39 Failed: 2) Failed tests: 28, 31 ./tests/bugs/bug-821056.t (Wstat: 0 Tests: 21 Failed: 1) Failed test: 15 ./tests/bugs/bug-908146.t (Wstat: 0 Tests: 10 Failed: 2) Failed tests: 8-9 ./tests/bugs/bug-913555.t (Wstat: 0 Tests: 11 Failed: 4) Failed tests: 4-6, 9 ./tests/bugs/bug-948686.t (Wstat: 0 Tests: 19 Failed: 8) Failed tests: 5-7, 9, 11, 13-15 ./tests/bugs/bug-948729/bug-948729-force.t (Wstat: 0 Tests: 35 Failed: 6) Failed tests: 29-31, 33-35 ./tests/bugs/bug-948729/bug-948729-mode-script.t (Wstat: 0 Tests: 35 Failed: 6) Failed tests: 29-31, 33-35 ./tests/bugs/bug-948729/bug-948729.t(Wstat: 0 Tests: 23 Failed: 2) Failed tests: 19, 23 Files=123, Tests=2019, 4834 wallclock secs ( 1.62 usr 0.25 sys + 258.83 cusr 201.05 csys = 461.75 CPU) Result: FAIL Thanks, Kiran. On Fri, Sep 26, 2014 at 9:32 PM, Lalatendu Mohanty wrote: > On 09/26/2014 02:59 AM, Justin Clift wrote: > >> On 25/09/2014, at 9:28 PM, Lalatendu Mohanty wrote: >> >> >>> Have we published somewhere which distributions or OS versions we are >>> running regression tests ? if not lets compile it and publish as this will >>> help community to understand which os distributions are part of the >>> regression testing. >>> >> The best we have so far is probably this: >> >>http://www.gluster.org/community/documentation/index. >> php/Using_the_Gluster_Test_Framework >> >> >> Do we have plans to run regression on a variety of distributions? Not >>> sure how difficult or complex it is to maintain. >>> >> The primary OS at the moment is CentOS 6.x (mainly due to it >> being the primary OS for GlusterFS I think). >> >> Manu and Harsha have been going through the regression tests >> recently, making them more cross platform in order to run on >> the BSDs. >> >> This effort has also highlighted some interesting Linux >> specific behaviour in the main GlusterFS code base, and led >> to fixes there. >> >> In short, we're all for running the regression tests on as >> many distributions as possible. If Community members want >> to put VM's or something online (medium-long term), I'd be >> happy to hook our Jenkins infrastructure up to them to >> automatically run tests on them. >> >> Is that kind of what you're asking? :) >> > > Yup, I will try to get a CentOS 7 instance for running regression tests :) > > -Lala > ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
