Expected behavior
Jenkins should produce an HTML report with the PR unit test changes and pylint reports.
Additional context and error message
Add any other context about the problem here, like error message and/or traceback. You might want to use triple back ticks to properly format it.
Impact of the bug Jenkins reports (both in CC7 and CC9) can break under certain circumstances.
Jenkins setups: CC7: https://cmssdt.cern.ch/dmwm-jenkins/job/DMWM-WMCore-PR-pylintpy3/
CC9: https://cmssdt.cern.ch/dmwm-jenkins/view/WMCore%20Docker/job/WMCore-PR-pylint/
Describe the bug The jenkins pylint json report sometimes misses the score, and the HTML report fails due to this.
How to reproduce it Create a report with jenkins on PR: https://github.com/dmwm/WMCore/pull/12123
The json pylint report created will be this: https://cmssdt.cern.ch/dmwm-jenkins/job/DMWM-WMCore-PR-pylintpy3/3471/artifact/pylintpy3Report.json/*view*/
As you can see, the first file is missing a "base" field. Other files do have the base field. Here is another report that works fine for comparison: https://cmssdt.cern.ch/dmwm-jenkins/job/DMWM-WMCore-PR-pylintpy3/3480/artifact/pylintpy3Report.json/*view*/
The filename specifically in this PR with the issue is WorkflowUpdater.py
Expected behavior Jenkins should produce an HTML report with the PR unit test changes and pylint reports.
Additional context and error message Add any other context about the problem here, like error message and/or traceback. You might want to use triple back ticks to properly format it.