Status: Fixed but Unreleased (View Workflow)
warnings plugin 4.51
I came up with the following workflow script brooken.groovy, which
compiles a file with clang, and then invokes the warnings plugin.
In the console log, there are warnings, but the warnings plugin detects zero warnings.
I modified the script slightly (fixed.groovy) by inserting a sleep statement before calling the warnings plugin. I re-ran the script and the warnings plugin detected the warnings.
It looks like the workflow-plugin is not providing the console to the warnings plugin when it needs it? Maybe a flush is missing?
- is duplicated by
JENKINS-42642 Warnings reported intermittently
- relates to
JENKINS-38381 [JEP-210] Optimize log handling in Pipeline and Durable Task
JENKINS-55215 Log from cmake/ctest steps isn't fully captured on OsX
- links to
I'm reopening so that I do not forget to remove the workaround in the warnings plugin.
I do have a build that reports this as a notice before instantly aborting
(the last line might lack a bunch of line breaks already from the start... stars were consumed by inserting it here):
[GNU C Compiler (gcc)] Sleeping for 5 seconds due to
[GNU C Compiler (gcc)] Parsing console log (workspace: '/home/jenkins/agent/workspace/workspace/<project_name>/build')
Unable to change directory using: .Entering directory (?<dir>.) to match Entering directory: D0750 0 deploy
I now have to guess if its related in some way to the ticket right here
(like some subdirs not yet present due to insufficient other process completion)
or if it is something totally different (that i was unable to clearly track down for now).
- Jenkins 2.346.3
- workflow-job / Pipeline Job plugin 1207.ve6191ff089f8
side note: if you had released your change already, then it would be less of a question, at least underneath this ticket.
Found the reported line and breakage to be unrelated to this ticket.
When doing some "scp" command with a "-v" flag for verbosity, then you might see messages like:
Entering directory: D0750 0 deploy
This will later on result in an error when doing some parsing with maybe e.g. warnings-ng (or similar).
The final line where the codes then will exit is of that format:
throw new ParsingException("Unable to change directory using: %s to match %s", makePath.toString(), line);
For now i will drop the "-v" switch - but i probably also will do some report to the respective tooling that fails to hard for such a line.
Please create an issue in the warnings plugin (or directly provide a PR that will improve the regular expression that scans for directory changes).
Ah thanks! Yes, that means I can remove my 5 sec sleep