[petsc-dev] broken nightlybuilds (next vs next-tmp)

Smith, Barry F. bsmith at mcs.anl.gov
Sat Nov 11 14:53:48 CST 2017


   There is no reason to waste time protesting the attempt to change to the new model. The attempt will happen as soon as we have the new test harness fully working. So help out or get out of the way.

  Barry


> On Nov 11, 2017, at 12:06 PM, Satish Balay <balay at mcs.anl.gov> wrote:
> 
> On Sat, 11 Nov 2017, Jed Brown wrote:
> 
>>> I don't think we have the resources to run full tests on every branch one
>>> at a time. Do we?
>> 
>> No,
> 
> Well the hope is - after the migration to new test suite is complete
> the cost of a full test run is lower. And we could somehow do fewer
> tests to capture most issues.
> 
>> and after each merge of a branch to 'master', the prospective merge
>> of other branches would need to be retested.  But the idea that the
>> automated test suite is infallible is also flawed.
> 
> Well arn't we relying on 'automated testing' with the current next
> model?
> 
> Satish



More information about the petsc-dev mailing list