Hi Pranith,
On 11/13/2014 06:57 AM, Pranith Kumar Karampuri wrote:
On 11/13/2014 03:23 AM, Justin Clift wrote:
Hi all,
At the moment, our smoke tests in Jenkins only run on a
replicated volume. Extending that out to other volume types
should (in theory :) help catch other simple gotchas.
On 11/13/2014 10:13 AM, Pranith Kumar Karampuri wrote:
On 11/13/2014 03:51 AM, Jeff Darcy wrote:
On the other hand, I'm not sure smoke is the place to do this.
Smoke is supposed to be a *quick* test to catch *basic* errors
(e.g. source fails to build) before we devote hours to a full
Hi all,
At the moment, our smoke tests in Jenkins only run on a
replicated volume. Extending that out to other volume types
should (in theory :) help catch other simple gotchas.
Xavi has put together a patch for doing just this, which I'd
like to apply and get us running:
\ At the moment, our smoke tests in Jenkins only run on a
replicated volume. Extending that out to other volume types
should (in theory :) help catch other simple gotchas.
Xavi has put together a patch for doing just this, which I'd
like to apply and get us running:
On 11/13/2014 03:23 AM, Justin Clift wrote:
Hi all,
At the moment, our smoke tests in Jenkins only run on a
replicated volume. Extending that out to other volume types
should (in theory :) help catch other simple gotchas.
Xavi has put together a patch for doing just this, which I'd
like to