In preparation for easybuilders/easybuild-easyblocks#157 I created this PoC.

The specification is (as documented):

    Check logTxt for messages matching regExps in order and do appropriate action
    :param logTxt: String containing the log, will be split into individual lines
    :param regExps: List of: regular expressions (as RE or string) to error on,
                    or tuple of regular expression and action (any of [IGNORE, WARN, ERROR])

In the end you'll get (if appropriate) a logged warning and an exception about the found issues.

I guess this function could even be split: 1 that returns the (warnings, errors) tuple and one that also increases errors_found_in_log, logs the warning and raises the exception (which would be the most common usage), but the name parse_log_for_error is already taken. Maybe name it parse_log_for_errors? The "old" parse_log_for_error can be implemented in terms of that but in can probably be simply deprecated. It is strange, does to much and yet almost nothing. Similar for parse_cmd_output. So for backwards compatibility I'd rather have EasyBlocks call check_log_for_errors directly and pass None as the regExp to run_cmd*