On 05/15/2014 09:08 PM, Luis Pabon wrote:
Should we create bugs for each of these, and divide-and-conquer?
That could be of help. First level of consolidation done (with frequency
of test failures) by Justin might be a good list to start with. If we
observe more failures as part of ongoing re
On 05/15/2014 07:57 PM, Niels de Vos wrote:
On Thu, May 15, 2014 at 06:05:00PM +0530, Vijay Bellur wrote:
On 04/30/2014 07:03 PM, Justin Clift wrote:
Hi us,
Was trying out the GlusterFS regression tests in Rackspace VMs last
night for each of the release-3.4, release-3.5, and master branches.
Should we create bugs for each of these, and divide-and-conquer?
- Luis
On 05/15/2014 10:27 AM, Niels de Vos wrote:
On Thu, May 15, 2014 at 06:05:00PM +0530, Vijay Bellur wrote:
On 04/30/2014 07:03 PM, Justin Clift wrote:
Hi us,
Was trying out the GlusterFS regression tests in Rackspace VMs
On Thu, May 15, 2014 at 06:05:00PM +0530, Vijay Bellur wrote:
> On 04/30/2014 07:03 PM, Justin Clift wrote:
> >Hi us,
> >
> >Was trying out the GlusterFS regression tests in Rackspace VMs last
> >night for each of the release-3.4, release-3.5, and master branches.
> >
> >The regression test is just
On 04/30/2014 07:03 PM, Justin Clift wrote:
Hi us,
Was trying out the GlusterFS regression tests in Rackspace VMs last
night for each of the release-3.4, release-3.5, and master branches.
The regression test is just a run of "run-tests.sh", from a git
checkout of the appropriate branch.
The go