[JIRA] (JENKINS-54833) Warnings Parser fails parsing log

[nolang...@gmail.com (JIRA)]

Title: Message Title

Norbert Lange commented on JENKINS-54833   Re: Warnings Parser fails parsing log I changes the source encoding and I now understand the issue (the new fake job still tried to read the files from the real jobs workspace). Some thoughts/inputs: 1) The log contained filenames that did not reside in the workspace and the plugin apparently does try to read and decode them, even if it then decides to do nothing with them. Means it bugged out for no reason [GNU Make + GNU C Compiler (gcc)] Copying affected files to Jenkins' build folder /var/jenkins_home/jobs/ztest/builds/19 [GNU Make + GNU C Compiler (gcc)] -> 0 copied, 2 not in workspace, 0 not-found, 0 with I/O error 2) If the filename points to a exe, DSO or object file, then no encoding setting will help - parsing will always fail (like for linker warnings). I have some custom messages about the object format and a fitting parser - not setting the linenumber or setting it to a negative value could indicate to skip source-file parsing, 3) failing to parse a file should not be an error (just as failing to copying the files is not).   Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.