canonical-ci-engineering team mailing list archive

["Stephen M. Webb" <stephen.webb@xxxxxxxxxxxxx>]

On 15-09-09 03:28 PM, Francis Ginther wrote:
> Let me clarify that 1.5 hour time increase. That only applies if you want to run these new builds as 'advisory' or not
> impacting the final result of the build. The reason for the long time in this case is that jenkins has to run the
> 'must-pass' jobs first and then the 'advisory' builds serially. In my proposal above, the "wily armhf (any real phone
> hw)" and "wily i386" jobs would be advisory. I only proposed this as a solution to addressing the currently broken tests
> without blocking unrelated MPs that would fail if the tests were just turned on as 'must-pass'.
> 
> If all of these jobs are 'must-pass' then they can all be executed concurrently and build times would be the same as
> they are today assuming nothing else is building and nothing has to wait for resources.

It looks like the end goal is that all build targets should be must-pass, but until the currently broken tests are fixed
that would be a show-stopper.

Is there a list of failing tests?


-- 
Stephen M. Webb  <stephen.webb@xxxxxxxxxxxxx>