Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-10097

Job stuck in a dead lock when running warning plugin

    Details

    • Similar Issues:

      Description

      I have the warnings plugin configured to scan the console log with "GNU compiler 4 (gcc)" only.
      Most of the times my builds stay stuck when the plugin is scanning the console log. The last message that I see in the console log is:

      [WARNINGS] GNU compiler 4 (gcc) : Found 4 warnings.

      The build is running on a slave, this jobs have a shared workspace with lots of files (svn checkout is done in the workspace and it's a huge project).

      There seems to be a deadlock during scanning of the workspace files. The jstack is in attachment.

        Attachments

          Issue Links

            Activity

            Hide
            snicoll Stéphane Nicoll added a comment -

            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.

            Show
            snicoll Stéphane Nicoll added a comment - 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.
            Hide
            drulli Ulli Hafner added a comment -

            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?

            Show
            drulli Ulli Hafner added a comment - 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?
            Hide
            snicoll Stéphane Nicoll added a comment -

            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.

            Show
            snicoll Stéphane Nicoll added a comment - 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.
            Hide
            drulli Ulli Hafner added a comment -

            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?

            Show
            drulli Ulli Hafner added a comment - 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?
            Hide
            drulli Ulli Hafner added a comment -

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

            Show
            drulli Ulli Hafner added a comment - I think the fix of JENKINS-14024 should help here too.

              People

              • Assignee:
                drulli Ulli Hafner
                Reporter:
                tadas Nuno Tadeu
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: