Bitten-Parser got confused

[anonymous]

for several strings the bitten parser seems to get confused and throws an internal error. But there shouldn't be any case in which the parser should break. The parser has to accept any input.

2009-11-13 18:16:41.089521500 [INFO    ] find . -name "*.di" -exec cp -f {} ../../../tango/{} \;
2009-11-13 18:16:41.113926500 [ERROR   ] Internal error in build step 'build'
2009-11-13 18:16:41.113929500 Traceback (most recent call last):
2009-11-13 18:16:41.113930500   File "/usr/local/lib/python2.5/site-packages/Bitten-0.7dev_r790-py2.5.egg/bitten/slave.py", line 327, in _execute_step
2009-11-13 18:16:41.113931500     step.execute(recipe.ctxt):
2009-11-13 18:16:41.113932500   File "/usr/local/lib/python2.5/site-packages/Bitten-0.7dev_r790-py2.5.egg/bitten/recipe.py", line 228, in execute
2009-11-13 18:16:41.113933500     ctxt.run(self, child.namespace, child.name, child.attr)
2009-11-13 18:16:41.113970500   File "/usr/local/lib/python2.5/site-packages/Bitten-0.7dev_r790-py2.5.egg/bitten/recipe.py", line 106, in run
2009-11-13 18:16:41.113971500     function(self, **args)
2009-11-13 18:16:41.113972500   File "/usr/local/lib/python2.5/site-packages/Bitten-0.7dev_r790-py2.5.egg/bitten/build/shtools.py", line 40, in exec_
2009-11-13 18:16:41.113973500     output=output, args=args, dir_=dir_)
2009-11-13 18:16:41.113974500   File "/usr/local/lib/python2.5/site-packages/Bitten-0.7dev_r790-py2.5.egg/bitten/build/shtools.py", line 142, in execute
2009-11-13 18:16:41.113984500     for out, err in cmdline.execute():
2009-11-13 18:16:41.113985500   File "/usr/local/lib/python2.5/site-packages/Bitten-0.7dev_r790-py2.5.egg/bitten/build/api.py", line 140, in execute
2009-11-13 18:16:41.113987500     line = line and _decode(line.rstrip().replace('\x00', ''))
2009-11-13 18:16:41.114000500   File "/usr/local/lib/python2.5/site-packages/Bitten-0.7dev_r790-py2.5.egg/bitten/build/api.py", line 47, in _decode
2009-11-13 18:16:41.114002500     return text.decode(sys.stdout.encoding, 'replace')

[osimons]

It may well be something with the files for input/output as reported/fixed by #504. Could you try the again using latest 0.6dev from repos?

BTW, your traceback paste seems to be cut prematurely - it does not contain the final line(s) with the actual error and location in code. Please paste traceback again if issue persists - and enclosing the paste in a {{{ }}} block to pre-format the input.