On Thu, 2015-08-13 at 19:07 +0100, Ian Jackson wrote:
> Ian Campbell writes ("[PATCH OSSTEST v3 2/2] cambridge: arrange to test
> each new baseline"):
> > Provide a new cr-daily-branch setting OSSTEST_BASELINES_ONLY which
> > causes it to only attempt to test the current baseline (if it is
> > unte
Ian Campbell writes ("[PATCH OSSTEST v3 2/2] cambridge: arrange to test each
new baseline"):
> Provide a new cr-daily-branch setting OSSTEST_BASELINES_ONLY which
> causes it to only attempt to test the current baseline (if it is
> untested) and never the tip version. Such tests will not result in
Provide a new cr-daily-branch setting OSSTEST_BASELINES_ONLY which
causes it to only attempt to test the current baseline (if it is
untested) and never the tip version. Such tests will not result in any
push.
Each new baseline is tested exactly once (i.e. we aren't repeating
hoping for a pass), he