On Thu, Oct 27, 2016 at 07:46:16AM -0400, Fritz Reese wrote:
> > Shouldn't something also remove dec_io_5.txt file if it is created?
> > Shall the (now xfailed, so not implemented yet?) runtime error terminate
> > the program, or can it be also just deleted later on? If not,
> > we'll need some dg-final cleanup-target-file or something similar that will
> > remote_file target delete the file (similarly to cleanup-modules etc.).
> >
> > Jakub
>
> For dec_io_5, the program (intentionally) crashes because "ACTION
> conflicts with READONLY" so dec_io_5.txt is never created.
So why dec_io_6.f90 worked at all (if it ever worked)?
And why the xfail when it works as expected?
>
> For dec_io_6, the "protected by READONLY" message is (intentionally) a
> runtime warning and does not terminate the program, so the following
> lines safely delete dec_io_6.txt.
>
> I am not familiar enough with DG to know whether there is a better way
> to express the intended behavior of the test programs. XFAIL is the
> closest thing I could determine.
Jakub
