• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • clearcase-plugin
    • None
    • Hudson version 1.380 on RHEL 5.3
      Hudson slave running 1.280 on RHEL 4.7
      clearcase plugin version 1.31

      Sometimes when running build we run into an error in the runLsHistory module.
      I wish I could provide more info but cannot. At this moment, if we run into this problem we run the build again and it works.

      14:08:58 [builder_RavenPlatMain_Chassis_Recommended] $ cleartool lshistory -all -since 15-oct-10.17:49:07utc+0000 -fmt '\"%Nd\" \"%u\" \"%En\" \"%Vn\" \"%e\" \"%o\" \"%[activity]p\" \n%c\n' -branch brtype:RavenPlatMain_Int -nco vobs/Raven3p vobs/ravenp/RavenPlat
      14:08:58 "20101015.140408" "builder" "/ccstore/builder/hudson/workspace/RavenPlatMain_Chassis_Recommended/builder_RavenPlatMain_Chassis_Recommended/vobs/ravenp/RavenPlat/platform/chassis_image/component_baselines.txt" "/main/RavenPlatMain_Int/16" "create version" "checkin" "chassis-buildnum--int-RavenPlatMain"
      14:08:58
      14:08:58 "20101015.135015" "builder" "/ccstore/builder/hudson/workspace/RavenPlatMain_Chassis_Recommended/builder_RavenPlatMain_Chassis_Recommended/vobs/ravenp/RavenPlat/scripts/buildnumbers/chassis-buildnum" "/main/RavenPlat_mainline/RavenPlatMain_Int/645" "create version" "checkin" "chassis-buildnum--int-RavenPlatMain"
      14:08:58 auto incrementing buildnumber to 184
      14:08:58
      14:08:58 FATAL: null
      14:08:58 java.lang.NullPointerException
      14:08:58 at hudson.plugins.clearcase.ucm.UcmHistoryAction.runLsHistory(UcmHistoryAction.java:175)
      14:08:58 at hudson.plugins.clearcase.history.AbstractHistoryAction.getChanges(AbstractHistoryAction.java:80)
      14:08:58 at hudson.plugins.clearcase.AbstractClearCaseScm.saveChangeLog(AbstractClearCaseScm.java:509)
      14:08:58 at hudson.plugins.clearcase.AbstractClearCaseScm.checkout(AbstractClearCaseScm.java:484)
      14:08:58 at hudson.model.AbstractProject.checkout(AbstractProject.java:1082)
      14:08:58 at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:479)
      14:08:58 at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:411)
      14:08:58 at hudson.model.Run.run(Run.java:1280)
      14:08:58 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
      14:08:58 at hudson.model.ResourceController.execute(ResourceController.java:88)
      14:08:58 at hudson.model.Executor.run(Executor.java:140)

          [JENKINS-7811] lshistory null bug

          peterkline added a comment -

          As a comparison this is the output of a build started one minute later after the first failure.

          14:09:57 [RavenPlatMain_Chassis_Recommended] $ cleartool desc -fmt %[found_bls]Xp\n stream:RavenPlatMain_Int@/vobs/tlv_pvob
          14:09:57 baseline:RAVENPLAT_MAIN_04-DEC-08_1815@/vobs/tlv_pvob
          14:09:57 [RavenPlatMain_Chassis_Recommended] $ cleartool desc -fmt %[component]Xp\n baseline:RAVENPLAT_MAIN_04-DEC-08_1815@/vobs/tlv_pvob
          14:09:57 component:tlv_comp@/vobs/tlv_pvob
          14:09:57 [RavenPlatMain_Chassis_Recommended] $ cleartool lsview builder_RavenPlatMain_Chassis_Recommended
          14:09:57 builder_RavenPlatMain_Chassis_Recommended /net/wsb-raven-dev5/ccstore/builder/builder_RavenPlatMain_Chassis_Recommended.vws
          14:09:57 [builder_RavenPlatMain_Chassis_Recommended] $ cleartool lsview -cview -s
          14:09:57 builder_RavenPlatMain_Chassis_Recommended
          14:09:57 [RavenPlatMain_Chassis_Recommended] $ cleartool desc -fmt %[found_bls]Xp\n stream:RavenPlatMain_Int@/vobs/tlv_pvob
          14:09:57 baseline:RAVENPLAT_MAIN_04-DEC-08_1815@/vobs/tlv_pvob
          14:09:57 [RavenPlatMain_Chassis_Recommended] $ cleartool desc -fmt %[component]Xp\n baseline:RAVENPLAT_MAIN_04-DEC-08_1815@/vobs/tlv_pvob
          14:09:57 component:tlv_comp@/vobs/tlv_pvob
          14:09:57 [builder_RavenPlatMain_Chassis_Recommended] $ cleartool pwv -root
          14:09:57 /ccstore/builder/hudson/workspace/RavenPlatMain_Chassis_Recommended/builder_RavenPlatMain_Chassis_Recommended
          14:09:57 [RavenPlatMain_Chassis_Recommended] $ cleartool lsview builder_RavenPlatMain_Chassis_Recommended
          14:09:57 builder_RavenPlatMain_Chassis_Recommended /net/wsb-raven-dev5/ccstore/builder/builder_RavenPlatMain_Chassis_Recommended.vws
          14:09:58 [builder_RavenPlatMain_Chassis_Recommended] $ cleartool lshistory -all -since 15-oct-10.18:08:57utc+0000 -fmt '\"%Nd\" \"%u\" \"%En\" \"%Vn\" \"%e\" \"%o\" \"%[activity]p\" \n%c\n' -branch brtype:RavenPlatMain_Int -nco vobs/Raven3p vobs/ravenp/RavenPlat
          14:09:58 [RavenPlatMain_Chassis_Recommended] $ cleartool lsview builder_RavenPlatMain_Chassis_Recommended
          14:09:58 builder_RavenPlatMain_Chassis_Recommended /net/wsb-raven-dev5/ccstore/builder/builder_RavenPlatMain_Chassis_Recommended.vws
          14:09:58 [builder_RavenPlatMain_Chassis_Recommended] $ cleartool lsview -cview -s
          14:09:58 builder_RavenPlatMain_Chassis_Recommended
          14:09:58 [RavenPlatMain_Chassis_Recommended] $ cleartool catcs -tag builder_RavenPlatMain_Chassis_Recommended

          peterkline added a comment - As a comparison this is the output of a build started one minute later after the first failure. 14:09:57 [RavenPlatMain_Chassis_Recommended] $ cleartool desc -fmt % [found_bls] Xp\n stream:RavenPlatMain_Int@/vobs/tlv_pvob 14:09:57 baseline:RAVENPLAT_MAIN_04-DEC-08_1815@/vobs/tlv_pvob 14:09:57 [RavenPlatMain_Chassis_Recommended] $ cleartool desc -fmt % [component] Xp\n baseline:RAVENPLAT_MAIN_04-DEC-08_1815@/vobs/tlv_pvob 14:09:57 component:tlv_comp@/vobs/tlv_pvob 14:09:57 [RavenPlatMain_Chassis_Recommended] $ cleartool lsview builder_RavenPlatMain_Chassis_Recommended 14:09:57 builder_RavenPlatMain_Chassis_Recommended /net/wsb-raven-dev5/ccstore/builder/builder_RavenPlatMain_Chassis_Recommended.vws 14:09:57 [builder_RavenPlatMain_Chassis_Recommended] $ cleartool lsview -cview -s 14:09:57 builder_RavenPlatMain_Chassis_Recommended 14:09:57 [RavenPlatMain_Chassis_Recommended] $ cleartool desc -fmt % [found_bls] Xp\n stream:RavenPlatMain_Int@/vobs/tlv_pvob 14:09:57 baseline:RAVENPLAT_MAIN_04-DEC-08_1815@/vobs/tlv_pvob 14:09:57 [RavenPlatMain_Chassis_Recommended] $ cleartool desc -fmt % [component] Xp\n baseline:RAVENPLAT_MAIN_04-DEC-08_1815@/vobs/tlv_pvob 14:09:57 component:tlv_comp@/vobs/tlv_pvob 14:09:57 [builder_RavenPlatMain_Chassis_Recommended] $ cleartool pwv -root 14:09:57 /ccstore/builder/hudson/workspace/RavenPlatMain_Chassis_Recommended/builder_RavenPlatMain_Chassis_Recommended 14:09:57 [RavenPlatMain_Chassis_Recommended] $ cleartool lsview builder_RavenPlatMain_Chassis_Recommended 14:09:57 builder_RavenPlatMain_Chassis_Recommended /net/wsb-raven-dev5/ccstore/builder/builder_RavenPlatMain_Chassis_Recommended.vws 14:09:58 [builder_RavenPlatMain_Chassis_Recommended] $ cleartool lshistory -all -since 15-oct-10.18:08:57utc+0000 -fmt '\"%Nd\" \"%u\" \"%En\" \"%Vn\" \"%e\" \"%o\" \"% [activity] p\" \n%c\n' -branch brtype:RavenPlatMain_Int -nco vobs/Raven3p vobs/ravenp/RavenPlat 14:09:58 [RavenPlatMain_Chassis_Recommended] $ cleartool lsview builder_RavenPlatMain_Chassis_Recommended 14:09:58 builder_RavenPlatMain_Chassis_Recommended /net/wsb-raven-dev5/ccstore/builder/builder_RavenPlatMain_Chassis_Recommended.vws 14:09:58 [builder_RavenPlatMain_Chassis_Recommended] $ cleartool lsview -cview -s 14:09:58 builder_RavenPlatMain_Chassis_Recommended 14:09:58 [RavenPlatMain_Chassis_Recommended] $ cleartool catcs -tag builder_RavenPlatMain_Chassis_Recommended

          Code changed in hudson
          User: : vlatombe
          Path:
          trunk/hudson/plugins/clearcase/src/main/java/hudson/plugins/clearcase/ucm/UcmHistoryAction.java
          http://jenkins-ci.org/commit/35983
          Log:
          JENKINS-7811 lshistory null bug

          SCM/JIRA link daemon added a comment - Code changed in hudson User: : vlatombe Path: trunk/hudson/plugins/clearcase/src/main/java/hudson/plugins/clearcase/ucm/UcmHistoryAction.java http://jenkins-ci.org/commit/35983 Log: JENKINS-7811 lshistory null bug

          I found the source for NPE.

          I seems to be triggered when you have a new set of foundation baselines and one component cannot be retrieved in the new set of baselines. For the next build it goes away probably because it compares against the previous build, so when it is relaunched the set of foundation baselines hasn't changed from the previous build.

          Vincent Latombe added a comment - I found the source for NPE. I seems to be triggered when you have a new set of foundation baselines and one component cannot be retrieved in the new set of baselines. For the next build it goes away probably because it compares against the previous build, so when it is relaunched the set of foundation baselines hasn't changed from the previous build.

          Fixed on trunk. When a component cannot be found in the new set of baselines, a message is issued and then the analysis goes on.

          Vincent Latombe added a comment - Fixed on trunk. When a component cannot be found in the new set of baselines, a message is issued and then the analysis goes on.

          I think this is related with the timestamper plugin that you use to obtain the timestamp in your logs. Could you try to disable it and see it the problem goes away. If so, you should try to upgrade the timestamper because old versions caused problems with plugins that analyze outputs like mercurial, or clearcase plugin (see JENKINS-7111)

          Vincent Latombe added a comment - I think this is related with the timestamper plugin that you use to obtain the timestamp in your logs. Could you try to disable it and see it the problem goes away. If so, you should try to upgrade the timestamper because old versions caused problems with plugins that analyze outputs like mercurial, or clearcase plugin (see JENKINS-7111 )

          peterkline added a comment -

          We are running the latest version of the timestamper plugin (1.2.1). We will disable anyway and retest.
          Thanks.

          peterkline added a comment - We are running the latest version of the timestamper plugin (1.2.1). We will disable anyway and retest. Thanks.

          peterkline added a comment -

          We verified this fix using a 1.3.2 nightly build the day after patching. This does fix our problem without having to remove the timestamper plugin. Thanks for the quick fix.

          peterkline added a comment - We verified this fix using a 1.3.2 nightly build the day after patching. This does fix our problem without having to remove the timestamper plugin. Thanks for the quick fix.

            vlatombe Vincent Latombe
            peterkline peterkline
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: