False error message not able to create fingerprint on jenkins console

[Bananeweizen]

Jenkins and plugins versions report

N/A

What Operating System are you using (both controller, and any agents involved in the problem)?

N/A

Reproduction steps

1. create a groovy parser which scans the console log (not some specific report file)
2. run the parser on a build which has console text that the groovy parser will match

Expected Results

no fingerprint error messages for the parser execution

Actual Results

It seems like there is one fingerprint related error entry per match of the groovy parser.

So the 113 in the image relates to the number of lines + the skipped 93 that are shown behind the warning icon:

Error Messages

Can't create fingerprints for some files:
- 'jenkins-console.log' file not found
- 'jenkins-console.log' file not found
- 'jenkins-console.log' file not found
- 'jenkins-console.log' file not found
- 'jenkins-console.log' file not found
- 'jenkins-console.log' file not found
- 'jenkins-console.log' file not found
- 'jenkins-console.log' file not found
- 'jenkins-console.log' file not found
- 'jenkins-console.log' file not found
- 'jenkins-console.log' file not found
- 'jenkins-console.log' file not found
- 'jenkins-console.log' file not found
- 'jenkins-console.log' file not found
- 'jenkins-console.log' file not found
- 'jenkins-console.log' file not found
- 'jenkins-console.log' file not found
- 'jenkins-console.log' file not found
- 'jenkins-console.log' file not found
- 'jenkins-console.log' file not found
  ... skipped logging of 93 additional errors ...

Anything else?

No response

Are you interested in contributing a fix?

No response

[uhafner]

This is a direct consequence of #3196

Don't you set the file name on your own in your parser?

It would make sense to skip the fingerprinting when the file name is the console log though...