This seems to be a common problem when using the ant workspace scanner. I think I need to find a better way to guess absolute file paths.

This is also a HUGE problem with clearcase dynamic views, where, even thought is only configured to look at console, it still looks at the workspace, and due to the insane stupdity of clearcase, all unix root filesystems are visible in /view/VIEW_NAME.

I see this as every symlink loop out in /home/user (from 15 years ago) left behind in the stdout as the symlink path is too long.....

Also, it would help if the plugin could check every 1000 files or so if the job has been cancelled?

if a job's XML contains

<parserConfigurations/>

does that tell the plugin to look at every file in the workspace and then check it against an empty list of parsers?

I have the same issue (no slave with a fresh install of Jenkins 1.473 and the latest version of the warnings plugin) for the Javac compiler (Eclipse).

En attente que Jenkins finisse de récupérer les données
channel stopped
[WARNINGS] Parsing warnings in console log with parser Java Compiler (Eclipse)

The first sentence is "Waiting for Jenkins to collect result" or something like that.

In the UI the job is completed (you can't monitor it) but the progression says that it's still running. I can't kill that job, I am forced to restart Jenkins.

Removing the warning plugin for the post-build action fixes the deadlock.

Can you please check if activating the new option to suppress the automatic but time expensive resolution of relative path names (JENKINS-14024, Release 4.7) helps?

I don't really understand what you mean here. You're talking about activating a new option to supress the resolution but all I get in the advanced section is Resolve relative paths which is unchecked (NOT enabled). I guess that's what you mean right (and it's the default anyway).

It's really the eclipse parser that is in trouble. I tried to use the standard Javac parser and my build completes as expected. So it's really about the eclipse compiler. Again, a fresh install of 1.473 with the warnings plugin and a simple job helped me to reproduce this behavior.

Ok, then your issue is a totally different one. Can you please create a new issue and attach the thread dump (see wiki on how to do that). How large is your console output?

I think the fix of JENKINS-14024 should help here too.