Re: Extended tests are now part of the test queue for Origin

What's the total runtime of the networking suite now? Are we seeing things merged that break it? > On Apr 19, 2016, at 1:59 AM, Maru Newby wrote: > > Can we consider adding the networking extended suite to the tests run > on every merge? It would like need to run as a 4th

Re: Extended tests are now part of the test queue for Origin

Can we consider adding the networking extended suite to the tests run on every merge? It would like need to run as a 4th job, though. On Wed, Apr 6, 2016 at 6:56 PM, Clayton Coleman wrote: > The test job for Origin now runs a subset of extended tests in a third > worker

Re: Extended tests are now part of the test queue for Origin

Not right now, but it's something good to queue up. On Apr 7, 2016, at 8:19 AM, David Eads wrote: The job won't block merge (yet) but please don't merge if there are > failures. > Will the bot be updated to make it clear which of the parallel jobs have failed? Given the

Re: Extended tests are now part of the test queue for Origin

HURRAY On Wed, Apr 6, 2016 at 8:56 PM, Clayton Coleman wrote: > The test job for Origin now runs a subset of extended tests in a third > worker whenever you add [test] (it'll be the third job when you click > through to Jenkins). The job won't block merge (yet) but

Extended tests are now part of the test queue for Origin

The test job for Origin now runs a subset of extended tests in a third worker whenever you add [test] (it'll be the third job when you click through to Jenkins). The job won't block merge (yet) but please don't merge if there are failures. The tests that are run are a subset of the full extended