Details
-
User Story
-
Resolution: Done
-
Not Evaluated
-
None
-
None
-
None
-
2
Description
4/12/12 5:33:32 AM EST: String found where operator expected at /build/recipes/179081964/base/sync.profile line 36, near ""libedit"" 4/12/12 5:33:32 AM EST: (Missing semicolon on previous line?) 4/12/12 5:33:32 AM EST: I couldn't parse /build/recipes/179081964/base/sync.profile, which I need to determine dependencies. 4/12/12 5:33:32 AM EST: The error was syntax error at /build/recipes/179081964/base/sync.profile line 36, near ""libedit"" 4/12/12 5:33:32 AM EST: at _qtqa_latest/scripts/qt/qtmod_test.pl line 444
parse_build_log could not extract any of this. It should be able to.
It would be rather dodgy to explicitly match that "I couldn't parse" line - this is a script we control, not some third-party thing, so we should be able to do something less fragile.
For example, introducing a "standard error format" from our own scripts which parse_build_log will always know how to parse.