[Swift-devel] dryrun for user

Mihael Hategan hategan at mcs.anl.gov
Thu Jul 25 15:32:25 CDT 2013


I think dryrun got removed in trunk (in the execution path, but I forgot
to remove it from the command line).

It was there along with "typecheck", which doesn't apply any more since
the swift compiler does the typechecking.

Is there a real need for dryrun any more? 

Mihael

On Thu, 2013-07-25 at 13:59 -0500, Justin M Wozniak wrote:
> Yes.
> 
> On 07/25/2013 12:46 PM, Mihael Hategan wrote:
> > Looks like a bug. Trunk?
> >
> > On Thu, 2013-07-25 at 11:06 -0500, Justin M Wozniak wrote:
> >> Ok.  I currently get:
> >>
> >> swift -dryrun -pgraph o.dot ~/hello-k.swift
> >>
> >> <java stack dump>
> >>
> >> Could not start execution:
> >>       import @ hello-k.kml, line: 5:
> >> org.globus.cog.karajan.analyzer.CompilationException: Import of
> >> 'swift.k' failed:
> >>       generateProvenanceGraph @ swift.k, line: 132:
> >> org.globus.cog.karajan.analyzer.CompilationException: Unknown function:
> >> generateProvenanceGraph:
> >>       java.lang.RuntimeException: Unknown function: generateProvenanceGraph
> >>
> >> On 07/25/2013 10:48 AM, Mihael Hategan wrote:
> >>> Dryrun should produce no output. It fakes app execution, but runs
> >>> through the dependencies.
> >>>
> >>> Mihael
> >>>
> >>> On Thu, 2013-07-25 at 10:30 -0500, Justin M Wozniak wrote:
> >>>> I was trying to get dryrun working for a user yesterday but can't figure
> >>>> out where the output went- is anyone else currently using this?
> >>>>        Thanks
> >>>>
> >>
> >
> 
> 





More information about the Swift-devel mailing list