On 05/07/2014, at 5:23 PM, Pranith Kumar Karampuri wrote:
hi Justin,
If the regression results complete before the smoke test then
'green-tick-mark' is over-written and people don't realize that the
regression succeeded by a simple glance at the list of patches. Can we do
anything
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
On 06/07/2014, at 8:24 AM, Pranith Kumar Karampuri wrote:
On 07/06/2014 12:36 PM, Justin Clift wrote:
snip
* 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
hi Justin,
If the regression results complete before the smoke test then
'green-tick-mark' is over-written and people don't realize that the
regression succeeded by a simple glance at the list of patches. Can we
do anything about it?
Pranith
On Sat, Jul 05, 2014 at 09:53:23PM +0530, Pranith Kumar Karampuri wrote:
hi Justin,
If the regression results complete before the smoke test then
'green-tick-mark' is over-written and people don't realize that the
regression succeeded by a simple glance at the list of patches. Can
we do
