[Swift-devel] swift-plot-log parsing errors

Allan Espinosa aespinosa at cs.uchicago.edu
Sun May 9 20:41:03 CDT 2010


I forgot to log the output of the build previoisly so I had to rerun the process
again.  Anyway, here's the target:

...
cat dostagein.event | sort -n -k 2 > dostagein.sorted-by-duration¬
plot-duration-histogram dostagein.sorted-by-duration
dostagein-duration-histogram.png¬
cat dostageout.event | sort -n -k 2 > dostageout.sorted-by-duration¬
plot-duration-histogram dostageout.sorted-by-duration
dostageout-duration-histogram.png¬
cat execute.transitions | sed 's/[^ ]* *[^ ]* \([^ ]*\).*/\1/' | sort | uniq >
execute.seenstates¬
trail execute¬
cat execute2.transitions | sed 's/[^ ]* *[^ ]* \([^ ]*\).*/\1/' | sort | uniq >
execute2.seenstates¬
trail execute2¬
info-and-karajan-actives
/home/aespinosa/workflows/cybershake/postproc-3sites_TEST.d/¬
(standard_in) 1: parse error¬
(standard_in) 1: parse error¬
(standard_in) 1: parse error¬
(standard_in) 1: parse error¬
(standard_in) 1: parse error¬
(standard_in) 1: parse error¬
(standard_in) 1: parse error¬
(standard_in) 1: parse error¬
(standard_in) 1: parse error¬
(standard_in) 1: parse error¬
(standard_in) 1: parse error¬
(standard_in) 1: parse error¬
(standard_in) 1: parse error¬
(standard_in) 1: parse error¬
...


i guess from here the series of targets are webpage -> pngs ->
info-and-actives.png -> execute2.event, karatasks.transitions 


On Sun, May 09, 2010 at 07:54:05PM +0000, Ben Clifford wrote:
> 
> > I get these parsing errors:
> 
> Look for the make target that this is part of.
> 
> i.e. read backwards in the '...' above until you find which file is being 
> parsed.
> 
> At least as I left it a year ago, the log plotting code was pretty fragile 
> wrt unexpected things, but you should be able to track down whats going on 
> with some poking.
> 
> -- 
> 
> 
> 



More information about the Swift-devel mailing list