Trivial bugs hurting progress

[Curtis Hovey-Canonical]

On Wed, Mar 4, 2015 at 8:44 AM, Martin Packman
<martin.packman at canonical.com> wrote:
> On 04/03/2015, Andrew Wilkins <andrew.wilkins at canonical.com> wrote:

> Curtis and I have talked about also doing a ppc64 test run as part of
> the gating job, that gets us the map ordering stuff as a newer go
> would, and other gccgo quirks covered as well. We don't want to bump
> the compiler version yet I think, as we want to be able to build with
> the trusty toolchain still, and not accidentally let in regressions by
> depending on newer gos.

I assume Core developers are like myself. I have run the test suite
just like the lander. I know a failure to merge is probably a bad
test.

As CI is running more compilers, series, and archs, We could prevent
regressions in master by using lesser combination that must pass. We
could:
- catch and fix map order bugs
- skip tests that wont pass on an arch/compiler combinations
- discover and fix real arch and series issues
without ever breaking the build, never blocking other engineers from merging.

We cannot achieve my ideal combination of precise, gcc-4.9+patches,
and ppc64el or i386. Precise doesn't work with ppc64el, and it is hard
to get a run 386 test quickly.


-- 
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui