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 <[email protected]> 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 job, though. > > On Wed, Apr 6, 2016 at 6:56 PM, Clayton Coleman <[email protected]> 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 please don't >> merge if there are failures. >> >> The tests that are run are a subset of the full extended suite and are >> defined in test/extended/conformance.sh. It includes all tests that >> are flagged with [Conformance] in both Kube and Origin. If you have >> extended tests in an area of function that demonstrate a core scenario >> and should be required on all merges, please add [Conformance] to the >> test description. Try to focus on the main path - don't just add the >> label to all the variations (those tests are run in the >> origin_extended job already post merge). >> >> Treat any flakes in the extended tests like our other tests and file >> issues with test/flake label. The upstream OOM score adjuster bug is >> causing deployments with very fast hooks to flake right now, and there >> may be a quota flake as well that we're looking into. >> >> _______________________________________________ >> dev mailing list >> [email protected] >> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev _______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
