builderrors reports eslint errors when none exist
Summary
builderrors reports eslint errors when none exist. Raised by @abhilash.maddireddy
Steps to reproduce
See https://code.gramener.com/dhfl/dhfl/-/jobs/53805
What is the current bug behavior?
eslint error reported with no errors.
What is the expected correct behavior?
No eslint error should be reported.
Possible fixes
@karmanya.aggarwal reports: I think what's happenening is that the split_error_warning (builderrorutils.py) is causing this problem due to the line 142, specifically, the way the if condition is set up, eslint's complexity check rule outputs an extra line 2 lines after its warnings - a '\n' and a '{number} problems \n' which are getting flagged as error lines. A simple fix would be to pass an Error match as well to that function.