[Gluster-devel] Problem with smoke, regression ordering
Niels de Vos
ndevos at redhat.com
Sat Jul 5 16:58:45 UTC 2014
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 anything about it?
This would likely be solved if we delay starting the regression testing
after a positive review was performed.
An other option is to enable more hosts to run the smoke tests. These
are currently only run on the main system and that is also used for
other jobs (some manual regression tests, release jobs, ...).
Do others have any other ideas or suggestions?
Niels
More information about the Gluster-devel
mailing list