WIP: support parsing pylint output
This parses pylint output with a simple regexp and counts one failure per message reported.
@kirr FYI, this is an old patch that's not really ready yet. I want to try integrating it in
software/slapos-testing
, with a really simple pylint config that only reports obvious errors and other things like https://pycodequ.al/docs/pylint-messages/w1201-logging-not-lazy.html that often come up during code review - that was the reason why I started doing this.I want to first have a test suite running and confirm that everything is OK first, until that it's probably to early to start looking at the code. I really don't know when I can finish this, but I was afraid of loosing the patch.
Thanks, @jerome. I think it could be a good idea to apply this code to master already with
WIP
orXXX not yet finished
marker. Then it won't get lost at all and whenever you or someone else has a chance to try running nxdtest over pylint we see from where to start, and we work step-by-step further until it works. In other words, please feel free to apply this patch to master with such a marker.Thanks again,
Kirillmentioned in commit jerome/nxdtest@0da1c3fd
mentioned in commit jerome/nxdtest@72e36088
added 3 commits
-
0da1c3fd...7b5add47 - 2 commits from branch
nexedi:master
- 72e36088 - support parsing pylint output
-
0da1c3fd...7b5add47 - 2 commits from branch
Thanks @kirr you are right, this patch is already passing the unit test so it's probably OK already
You are welcome, @jerome. Thanks for bringing these updates to nxdtest.