[petsc-dev] 'master' RESET after bad merge! - 'tisaac/thplex' was based on 'next'

Matthew Knepley knepley at gmail.com
Thu Sep 4 11:52:41 CDT 2014


On Thu, Sep 4, 2014 at 11:46 AM, Jed Brown <jed at jedbrown.org> wrote:

> Matthew Knepley <knepley at gmail.com> writes:
> > It is important to check things that do happen. If bears do wander in
> > the cockpit
>
> This does happen, yes.
>
> > and are not noticed for some time, then this would be important to
> > automate.
>
> The entire purpose of the inspection is to certify that various parts,
> including instruments and controls in the cockpit, are functional.  The
> only way to not notice the bear is to have not done the inspection, in
> which case you have no business signing the certificate.  There is no
> point in automating the bear check because your primary duty of
> inspecting the instruments and controls is not automated and you can't
> do that inspection without noticing the bear.
>

And I do not believe that there is "no way" that this check would not be
missed.
I know you do. I think you suffer from lack of imagination. This is a fatal
flaw when
designing fault tolerant systems.

   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/20140904/15c880e1/attachment.html>


More information about the petsc-dev mailing list