[2019-11-19T19:23:10.596Z] at org.sonar.api.utils.command.CommandExecutor.execute(CommandExecutor.java:102)
[2019-11-19T19:23:10.596Z] at org.sonar.plugins.python.pylint.PylintArguments.pylintVersion(PylintArguments.java:45)
[2019-11-19T19:23:10.596Z] at org.sonar.plugins.python.pylint.PylintArguments.<init>(PylintArguments.java:37)
[2019-11-19T19:23:10.596Z] at org.sonar.plugins.python.pylint.PylintIssuesAnalyzer.<init>(PylintIssuesAnalyzer.java:46)
[2019-11-19T19:23:10.596Z] at org.sonar.plugins.python.pylint.PylintSensor.createAnalyzer(PylintSensor.java:105)
[2019-11-19T19:23:10.596Z] at org.sonar.plugins.python.pylint.PylintSensor.initializeAnalyzer(PylintSensor.java:95)
[2019-11-19T19:23:10.596Z] at org.sonar.plugins.python.pylint.PylintSensor.execute(PylintSensor.java:69)
Analysis still marked as successful
steps to reproduce: execute analysis with sonar.python.pylint.reportPath and make sure pylint binary is missing or not executable from PATH.
Even though execution of pylint during analysis is deprecated on all OSes, it appears Pylint remains executed when sonar.python.pylint.reportPath is set, just to get the version of pylint. See: