[Gluster-infra] [Gluster-devel] Jenkins success/failure with *BSD thought

Justin Clift justin at gluster.org
Mon Jul 28 12:55:01 UTC 2014

On 28/07/2014, at 1:41 PM, Kaleb S. KEITHLEY wrote:
> To me a smoke test should be a simple compile and run the executable(s)
> to make sure they don't crash with the most basic configuration.
> I think the posix tests that are in smoke.sh today should really be part
> of the regression test, e.g. .../basic/posix.t
> For one thing it'd make the smoke.sh run faster.

It should be pretty simple to move the smoke.sh test into the
regression testing job instead.  Add some logic so that if the
smoke test fails, the regression test doesn't run either (and
the whole thing gets marked as bad).

Other thoughts on this stuff? :)

+ 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-infra mailing list