[petsc-dev] Configure push

[Matthew Knepley]

On Mon, Jun 6, 2016 at 5:27 PM, Satish Balay <balay at mcs.anl.gov> wrote:

> Matt,
>
> Per integration workflow - all feature branches should be tested
> locally (and be complete) - before merged to next [next is for
> integration testing - not feature testing]
>
> You could have used (modified):
>
> config/examples/arch-linux-xsdk-dbg.py
> config/examples/arch-osx-xsdk-opt.py
>
> Yeah - we don't have automatic 'feature branch test before integration
> testing' workflow - so currently this has to be done manually.


I don't really have the OS/compiler options available to test things
exhaustively, so I am
using next for this. I think this is acceptable right now.

  Thanks,

    Matt


>
> Satish
>
> On Mon, 6 Jun 2016, Matthew Knepley wrote:
>
> > I have pushed configure changes to next. They mainly concern the changes
> > made to support xSDK. Do we have a nightly test for this?
> >
> > Those changes broke the configure encapsulation by directly depending on
> > PETSc. I have removed this dependence, but it would be good if we checked
> > that this did not break anything for xSDK.
> >
> >   Thanks,
> >
> >      Matt
> >
> >
>
>


-- 
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20160606/1fd8ca53/attachment.html>