[Gluster-devel] Problem with smoke, regression ordering
Pranith Kumar Karampuri
pkarampu at redhat.com
Sun Jul 6 07:24:51 UTC 2014
On 07/06/2014 12:36 PM, Justin Clift wrote:
> On 06/07/2014, at 8:03 AM, Justin Clift wrote:
> <snip>
>> There are a few ways we could address this:
>>
>> * Adjust the smoke test job so it runs on the Rackspace
>> slaves
>>
>> Hopefully not hard. But not sure. We can try it out.
>>
>> * Change the triggered regression test, so it doesn't
>> start automatically like this.
>
> * We could also disable the old "regression" job, so it
> doesn't run on build.gluster.org.
This only reduces the race window. Doesn't fix the problem ;-). But I
see your point. It is definitely better to not use build.gluster.org for
regressions.
Pranith
>
> Would stop the queuing problems. ;)
>
> + Justin
>
> --
> 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
>
More information about the Gluster-devel
mailing list