> I've discussed this idea with different people before. But the major concern
> was how do we identify that minimal set of basic tests that would do a good
> job of identifying most regressions. Considering that regression suite will
> keep growing and will take longer to complete in the future, n
On Tue, Jun 23, 2015 at 05:49:57AM -0400, Kaleb Keithley wrote:
>
> That history for the last 16 hours is mainly me triggering builds
> manually. When I submit regression tests manually they're never picked
> up unless I go kick off-line slaves – they never wake up by
> themselves.
>
> New change
That history for the last 16 hours is mainly me triggering builds manually.
When I submit regression tests manually they're never picked up unless I go
kick off-line slaves – they never wake up by themselves.
New changes submitted to gerrit in the last 24 hours have not had any automatic
regre
On Mon, Jun 22, 2015 at 08:31:49PM -0400, Kaleb Keithley wrote:
>
> I've rebooted many of the slaves, but most of them are still sitting
> idle and about 90% of the changes submitted in the last 12+ hours have
> not had their regression tests run.
>
> Anyone have any ideas?
I dont know, the queu
