On Friday 16 November 2012 05:01 PM, Paul Sokolovsky wrote:

Public bug reported:

It might seems that result parsing support should be optional, for the case it's really needed (because otherwise results can already be in format LAVA expects). However, trying testdef without "parse" section leads to:

<LAVA_DISPATCHER>2012-11-16 01:25:05 PM INFO: Downloading image: http://192.168.15.225:38713/fs.tgz <LAVA_DISPATCHER>2012-11-16 01:25:06 PM ERROR: error processing results for: 0_cbuild-gcc-1353061077 Traceback (most recent call last): File "/home/pfalcon/devel/linaro/lava/lava-dispatcher/lava_dispatcher/lava_test_shell.py", line 207, in get_bundle testruns.append(_get_test_run(results_dir, d, hwctx, swctx)) File "/home/pfalcon/devel/linaro/lava/lava-dispatcher/lava_dispatcher/lava_test_shell.py", line 172, in _get_test_run 'test_results': _get_test_results(testdef, stdout), File "/home/pfalcon/devel/linaro/lava/lava-dispatcher/lava_dispatcher/lava_test_shell.py", line 121, in _get_test_results pattern = re.compile(testdef['parse']['pattern']) KeyError: 'parse'

I just pushed a branch with code changes required to fix the above. I request someone to review the following:

https://code.launchpad.net/~stylesen/lava-dispatcher/fix-empty-parse-pattern...

Thank You.