[Swift-user] Known issue with stdout and stderr file delays?

[Mihael Hategan]

Hi Mike and Jonathan,

I'm afraid I need more context. I am unable to reproduce the issue,
although I did discover another bug in the way FixedArrayMapper parses
strings.

Can you please tell me what array mapper we are talking about, what the
app signature is, what provider you are using, and whether provider
staging is enabled or not.

Better yet, please send me the swift log if you can.

Mihael

On Wed, 2014-05-28 at 18:22 -0500, Michael Wilde wrote:
> On 5/28/14, 5:01 PM, Jonathan Ozik wrote:
> > Hi all,
> >
> > Has anyone run into issues when trying to direct stdout and stderr to output files and getting the error:
> > Caused by: The following output files were not created by the application: sim.out, err.out
> This seems to be caused by an error in Swift (based on investigating 
> with Jonathan off-list).
> 
> The bug is that if an app returns an array of files, then any non-array 
> returns from the app are not getting handled correctly.
> It seems to be a problem in the array-collecting code in the Swift 
> app-launching wrapper, which may be loosing its directory context after 
> returning from the collection function.
> >
> > It looks like the files are being created too late and not caught when the output is being gathered up? This is using trunk, by the way.
> >
> > Also, in a related question, is there an easy way to redirect stdout and stderr from an app invocation to the regular swift.out without creating specific files?
> No, not at the moment. Some variations of this capability have been 
> discussed, though. It seems to me to be a useful addition to implement.
> 
> - Mike
> >
> > Jonathan
> >
> > _______________________________________________
> > Swift-user mailing list
> > Swift-user at ci.uchicago.edu
> > https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-user
>