[petsc-dev] upcoming release and testing

Matthew Knepley knepley at gmail.com
Mon Apr 2 08:55:13 CDT 2018


On Sun, Apr 1, 2018 at 5:12 PM, Satish Balay <balay at mcs.anl.gov> wrote:

>
> I've merged the following branches [tested in next-tmp] to master.
>
> http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/
> 2018/04/01/next-tmp.html
>
> origin/jed/fix-analyzer-bugs
> origin/balay/update-hypre-v2.14.0
> origin/denera/tao-lmvm-info-bugfix
> origin/knepley/feature-med-pkg
> origin/knepley/fix-hdf5-attribute
> origin/knepley/test-allow-line-continuation
> origin/balay/update-zoltan-v3.83
>

Great.


> The outstanding branches in next are:
>
>   origin/knepley/fix-cylinder-mesh
>   origin/knepley/fix-dm-gmg
>   origin/knepley/fix-ex62-tests
>   origin/knepley/fix-fe-bd-integral
>   origin/knepley/fix-fe-vector-spaces
>   origin/knepley/fix-snes-ex69
>   origin/tisaac/feature-dmfield
>

origin/knepley/fix-cylinder-mesh
origin/knepley/fix-dm-gmg
origin/knepley/fix-ex62-tests

should all go clean. Can we try those in next-tmp whenever you have a
chance.


> So any issues in 'next' that are not in 'master' are likely due to these
> branches.
>
> http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/01/next.html
> http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/
> 2018/03/31/master.html
>
> Matt, Toby - can you take a look at these issues?
>

Yes.

  Thanks,

     Matt


> If needed - we can schedule one branch at a time in next-tmp testing.
>
> Thanks,
> Satish
>



-- 
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

https://www.cse.buffalo.edu/~knepley/ <http://www.caam.rice.edu/~mk51/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20180402/3d30a1c6/attachment.html>


More information about the petsc-dev mailing list