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

[Satish Balay]

On Sun, 12 Nov 2017, Matthew Knepley wrote:

> On Sat, Nov 11, 2017 at 9:40 PM, Satish Balay <balay at mcs.anl.gov> wrote:
> 
> > [Starting a new thread for this]
> >
> > Tonight's builds will be on 'next-tmp' with:
> >
> 
> How easy would it be to setup a system that throttles (or in some way
> intelligently selects) the branches
> for 'next'? And when a branch graduates to master, or is withdrawn, it
> takes a new branch.

You are refering to improvements in the test infrastructure we were
discussing in the other theread yesterday. Haven't everyone wanted to
postpone this discussion to later?

Satish

> 
>    Matt
> 
> 
> > $ git fetch -p && comm -12 <(git branch -r --merged origin/next-tmp |
> > sort) <(git branch -r --no-merged origin/master | sort) |grep -v '
> > origin/next-tmp'
> >   origin/barry/add-bcaste-log
> >   origin/barry/fix-pastix-interface
> >   origin/jed/variadic-malloc
> >   origin/knepley/feature-plex-l2-projection
> >   origin/stefano_zampini/feature-glvis-supportdmcomposite
> >   origin/tmunson/tao-pounders-fix-code
> >
> > reference: branches are clean on es with
> > ./bin/maint/buildtest arch-linux-cxx-cmplx-pkgs-64idx
> > ./bin/maint/buildtest arch-linux-pkgs-opt
> >
> > Satish
> >
> 
> 
> 
>