[petsc-dev] Fluent test

Matthew Knepley knepley at gmail.com
Sat Feb 11 14:01:20 CST 2017


On Sat, Feb 11, 2017 at 1:59 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:

>
>   Matt,
>
>     I see the following
>
> 249b02ff src/dm/impls/plex/examples/tests/ex1.c    (Matthew Knepley
> 2017-01-19 14:34:09 -0600 386)     requires: broken
>
> so it looks like you previously thought it was broken and hence marked it
> this way.
>
> I added
>
> 7f662ca5 src/dm/impls/plex/examples/tests/ex1.c    (Barry Smith
>  2017-02-09 14:38:55 -0600 387)     requires: !complex
>
> which apparently broke the previous broken requires and hence triggered
> the "error" you could not fix.
>
> I have put both requires on the same line and the test harness now
> correctly does not run this example since it requires broken.


Thanks. I went through it carefully with the debugger now, and I don't
think it ought to be broken, but obviously the problem has
been there for some time. I think it is connected to mixing ASCII and
binary reads to the file, which might be opened in the wrong mode.

  Thanks,

     Matt


> > On Feb 11, 2017, at 9:10 AM, Matthew Knepley <knepley at gmail.com> wrote:
> >
> > This test
> >
> >   dm_impls_plex_tests-runex1_fluent_3
> >
> > mysteriously stopped working when I pulled. I stepped through and a
> read() call returns
> > EOF when its clearly not at the end. I have no idea how to debug. Did
> someone just change
> > something connected with binary reading, file opening, Fluent?
> >
> >    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
>
>


-- 
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/20170211/fbbe67c2/attachment.html>


More information about the petsc-dev mailing list