[petsc-dev] broken nightlybuilds (next vs next-tmp)
Satish Balay
balay at mcs.anl.gov
Tue Nov 7 13:13:52 CST 2017
I think so.
Also do 'make alltests DIFF=$PETSC_DIR/bin/petscdiff' [esp with
feature changes that are likely to break things] and fix regressions -
before a PR or a merge to next.
But I don't think most of us are doing this..
Satish
On Mon, 6 Nov 2017, Patrick Sanan wrote:
> Should this be considered standard practice for all contributors?
>
> On Mon, Nov 6, 2017 at 4:19 PM, Satish Balay <balay at mcs.anl.gov> wrote:
>
> > On Sun, 5 Nov 2017, Satish Balay wrote:
> >
> > > > origin/jed/fix-stdout-attr-delete
> > > > origin/jed/pastix-comm
> > > > origin/mark/fix-mat
> > >
> > > These are now merged to master.
> >
> > Jed, Mark,
> >
> > The above branches appear to have started from maint. Are they destined
> > to maint?
> >
> > If so it would be good to make it more obvious with a '/maint' suffix in
> > the branch name.
> >
> > Thanks,
> > Satish
> >
>
More information about the petsc-dev
mailing list