Error messages

4 views
Skip to first unread message

Jeffrey Micher

unread,
Jan 23, 2013, 10:38:42 AM1/23/13
to ducttap...@googlegroups.com
As I'm working through trying to learn ducttape, I'm getting some error messages that I don't understand.  I tried 1 simple workflow, then edited it to name the output file with a name of choice rather than with the name of the variable.  So that I would start fresh, I removed the directories from the previous run. I rerun the tape, and I get:
 
 ducttape preprocess.tape -p Tokenize
ducttape 0.3-pre1
by Jonathan Clark
WARNING: 1 corrupt or incomplete workflow versions found. Ignoring them. (This could be due to upgrading from an older version of ducttape that doesn'\
t support versioning)
Have 0 previous workflow versions
Discovering plan
Finding hyperpaths contained in plan...
Found 1 vertices implied by realization plan Tokenize
Union of all planned vertices has size 1
Discovering versions
Loading workflow version history...
WARNING: 1 corrupt or incomplete workflow versions found. Ignoring them. (This could be due to upgrading from an older version of ducttape that doesn'\
t support versioning)
Checking for completed tasks
Finding packages...
Found 1 packages
Checking for already built packages...
Checking inputs...
Work plan (arbitrary traversal):
^[[32mRUN:^[[0m /home/jmicher/canonical/./^[[36mtok_en^[[0m/^[[34mBaseline.baseline^[[0m (^[[33mBaseline.baseline^[[0m)
Are you sure you want to run these 1 tasks? [y/n] y
Exception in thread "main" java.lang.RuntimeException: Version history directory already exists (this is probably a bug in ducttape. please report it.\
 for now, you can try deleting the directory): /home/jmicher/canonical/./.versions/1
        at ducttape.versioner.WorkflowVersionStore$.create(WorkflowVersionStore.scala:97)
        at ducttape.cli.ExecuteMode$.run(ExecuteMode.scala:113)
        at Ducttape$$anonfun$main$9.apply(ducttape.scala:872)
        at ducttape.cli.ErrorUtils$.ex2err(ErrorUtils.scala:59)
        at Ducttape$.main(ducttape.scala:573)
        at Ducttape.main(ducttape.scala)
^[[0m
^[[0m
 
So, I looked in /home/jmicher/canonical/.. and there is no ./versions directory.  So I don't know where it is to delete it.
 
Also, any idea why I'm getting stdout containing things starting with ^[[ ?
 
Jeffrey

Matthew Gardner

unread,
Jan 23, 2013, 10:51:52 AM1/23/13
to Jeffrey Micher, ducttap...@googlegroups.com
On Wed, Jan 23, 2013 at 10:38 AM, Jeffrey Micher <jmi...@cs.cmu.edu> wrote:
So, I looked in /home/jmicher/canonical/.. and there is no ./versions directory.  So I don't know where it is to delete it.

Just to be sure this isn't a simple error, ducttape would have created a ./.versions directory, not a ./versions directory.  Did you look for ./.versions, and just type it wrong in your email, or did you only look for ./versions?

Jeffrey Micher

unread,
Jan 23, 2013, 11:02:44 AM1/23/13
to ducttap...@googlegroups.com
I copied and pasted the error message.  I did find the .versions directory and deleted it.  Ran again and it worked.  But then I edited my tape file and ran it again and got the same message.
 
So the question I guess is: what should the procedure be when incrementally developing and testing a .tape file (to avoid getting errors)?

Jonathan Clark

unread,
Jan 23, 2013, 11:04:09 AM1/23/13
to Jeffrey Micher, ducttap...@googlegroups.com
Hi Jeff,

This was a bug in v0.3-pre1. Downloading v0.3-pre3 should fix the crashing issue.

The ^[[ lines are ANSII color codes, which will display fine on most interactive Linux consoles. You can disable them with --no_color.

-Jon


On Wed, Jan 23, 2013 at 10:38 AM, Jeffrey Micher <jmi...@cs.cmu.edu> wrote:
 
Jeffrey

--
 
 

Nathan Schneider

unread,
Jan 23, 2013, 11:21:07 AM1/23/13
to Jeffrey Micher, ducttap...@googlegroups.com
On Wed, Jan 23, 2013 at 11:02 AM, Jeffrey Micher <jmi...@cs.cmu.edu> wrote:
I copied and pasted the error message.  I did find the .versions directory and deleted it.  Ran again and it worked.  But then I edited my tape file and ran it again and got the same message.
 
So the question I guess is: what should the procedure be when incrementally developing and testing a .tape file (to avoid getting errors)?

In general, if you want to modify a task after it has been run successfully, rather than delete stuff ducttape has generated you can invalidate a result—something like:

$ ducttape workflow.tape invalidate task '*'

where 'task' is the task you want to invalidate.

Nathan
--
 
 

Reply all
Reply to author
Forward
0 new messages