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

Modules marqued as (didn't run) after succesful Build

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • maven-plugin
    • None
    • Jenkins ver. 1.532.2
      Maven Project Plugin 2.0

      After a successful Build some Maven modules appear in Grey (didn't run) (while successful in the console output), which seems to have an impact on the test results.
      "Show all failed test>>>" link doesn't show up, and it is impossible to see the results of the tests.
      After 5 days we were able to see the tests and the jobs were green from the same Build.
      We encountered this problem a couple of times.

      This might be related to the Issue JENKINS-7848

          [JENKINS-26644] Modules marqued as (didn't run) after succesful Build

          satya b added a comment -

          I too getting same problem oftenly from last few weeks. all module builds are all success but its not showing green and appears as grey. also as Bahir mentioned these builds are impact on test results also.

          jenkins version is 1.528 and Maven Project Plugin version is 1.528

          satya b added a comment - I too getting same problem oftenly from last few weeks. all module builds are all success but its not showing green and appears as grey. also as Bahir mentioned these builds are impact on test results also. jenkins version is 1.528 and Maven Project Plugin version is 1.528

          Ulf Hedlund added a comment -

          We encountered the same problem today, in about 10 built modules only three of them were marked as built, the rest said "Did not build". We resolved the problem by using "Delete All Disabled Modules" in the left menu for the job. After that everything worked fine again, and even older builds suddenly reported all modules as successfully built.

          I believe that the following Jenkins log is related to the broken build (but I cannot say for sure because the server is under quite heavy load):

          SEVERE: Trying to unexport an object that's already unexported
          java.lang.IllegalStateException: Invalid object ID 3188 iota=4620
          at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:348)
          at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:371)
          at hudson.remoting.Channel.unexport(Channel.java:612)
          at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:38)
          at hudson.remoting.Channel$2.handle(Channel.java:483)
          at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60)
          Caused by: java.lang.Exception: Object appears to be deallocated at lease before Wed May 27 10:51:58 CEST 2015
          at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:344)
          ... 5 more

          Ulf Hedlund added a comment - We encountered the same problem today, in about 10 built modules only three of them were marked as built, the rest said "Did not build". We resolved the problem by using "Delete All Disabled Modules" in the left menu for the job. After that everything worked fine again, and even older builds suddenly reported all modules as successfully built. I believe that the following Jenkins log is related to the broken build (but I cannot say for sure because the server is under quite heavy load): SEVERE: Trying to unexport an object that's already unexported java.lang.IllegalStateException: Invalid object ID 3188 iota=4620 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:348) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:371) at hudson.remoting.Channel.unexport(Channel.java:612) at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:38) at hudson.remoting.Channel$2.handle(Channel.java:483) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: java.lang.Exception: Object appears to be deallocated at lease before Wed May 27 10:51:58 CEST 2015 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:344) ... 5 more

          I too have seen the same issue on Jenkins ver. 1.609.2, my guess is while creating new job when we copy it from existing one then it is not being copied properly.

          avinash mishra added a comment - I too have seen the same issue on Jenkins ver. 1.609.2, my guess is while creating new job when we copy it from existing one then it is not being copied properly.

            Unassigned Unassigned
            hicham Hicham Bahir
            Votes:
            4 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: