Karl Rupp writes:
> Hi Patrick,
>
>> Once tuning is complete, how is one intended to interpret the nice green
>> check marks? "The library compiles" or "All the tests passed"?
>
> So far the green checkmark essentially means "The library compiles". We
> are working towards "All the tests passed
On Fri, Jul 20, 2018 at 4:28 PM PETSc checkBuilds <
petsc-checkbui...@mcs.anl.gov> wrote:
>
>
> Dear PETSc developer,
>
> This email contains listings of contributions attributed to you by
> `git blame` that caused compiler errors or warnings in PETSc automated
> testing. Follow the links to see
Hi Patrick,
Once tuning is complete, how is one intended to interpret the nice green
check marks? "The library compiles" or "All the tests passed"?
So far the green checkmark essentially means "The library compiles". We
are working towards "All the tests passed", but that requires some more
Dear petsc-dev,
I'm once again revisiting doing "proper" checkpoint-restart cycles. I would
like to leverage the existing PETSc stuff for this as much as possible, but I
am a bit lost as to what is implemented, and what is missing.
I have:
- A (distributed) DMPlex defining the topology
- Som
This is super cool - thanks Alp and Karl!
Once tuning is complete, how is one intended to interpret the nice green
check marks? "The library compiles" or "All the tests passed"?
I ask because in the demo PR there is the reassuring check mark and "3 of 3
builds passed", even though failed tests ar
