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

ClearCase error after user canceled previous update

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      See http://hudson.361315.n4.nabble.com/ClearCase-error-after-user-canceled-previous-update-td2242261.html for the complete thread.

      A user canceled a job while it was in the middle of updating the view:

      Processing dir "xxx\domain\dev\config\com\xxx\spr\domain\search".
      ......SCM check out aborted
      Recording test results
      ..ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver aborted due to exception
      java.lang.InterruptedException
      at java.lang.Object.wait(Native Method)
      at hudson.remoting.Request.call(Request.java:122)
      at hudson.remoting.Channel.call(Channel.java:551)
      at hudson.FilePath.act(FilePath.java:742)
      at hudson.FilePath.act(FilePath.java:735)
      at hudson.tasks.junit.JUnitParser.parse(JUnitParser.java:83)
      at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:122)
      at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:133)
      at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
      at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:601)
      at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:580)
      at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:558)
      at hudson.model.Build$RunnerImpl.post2(Build.java:158)
      at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:528)
      at hudson.model.Run.run(Run.java:1264)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
      at hudson.model.ResourceController.execute(ResourceController.java:88)
      at hudson.model.Executor.run(Executor.java:124)
      Email was triggered for: Failure
      Sending email for trigger: Failure
      Sending email to: [hidden email]
      Finished: FAILURE

      The job is marked as a failure, which isn't unexpected. So far, so good.

      However, now ClearCase always thinks that this job's view is in the middle of an update, so subsequent runs fail:

      Started by an SCM change
      Building remotely on NODE5
      [NODE5_jobx] $ cleartool pwv -root
      C:\Hudson\workspace\jobx\NODE5_jobx
      [jobx] $ cleartool lsview NODE5_jobx
      NODE5_jobx \\NODE5\view\viewdb\NODE5_jobx
      [NODE5_jobx] $ cleartool lsview -cview -s
      NODE5_jobx
      [jobx] $ cleartool catcs -tag NODE5_jobx
      element * CHECKEDOUT
      element * .../viewx_dev/LATEST
      mkbranch viewx_dev
      element * .../viewx/LATEST
      element * IH_REL1234
      element * /main/LATEST
      load \xxx
      [NODE5_jobx] $ cleartool update -force -overwrite -log NUL
      cleartool: Warning: An update is already in progress for view "C:\Hudson\workspace\jobx\NODE5_jobx".
      Started by 'rsteele@NODE5' (process 2064) on 6/2/2010 2:46:36 PM
      Continue, terminating the previous update session? [no] FATAL: java.io.IOException: View update failed: cleartool: Warning: An update is already in progress for view "C:\Hudson\workspace\jobx\NODE5_jobx".
      Started by 'rsteele@NODE5' (process 2064) on 6/2/2010 2:46:36 PM
      Continue, terminating the previous update session? [no]
      Recording test results
      Email was triggered for: Failure
      Sending email for trigger: Failure
      Sending email to: [hidden email]
      Finished: FAILURE

      I believe this is the correct behavior on Hudson's part: it thinks an update is already in progress so to be safe it fails the build. The problem is that the view is forever wedged in this state.

      I'm wondering if this has something to do with how the original update was aborted. Is there a way to make sure the view is clean after the abort?

      I'm running Hudson 1.360 with Windows XP master and slaves, using version 1.2 of the ClearCase plugin with Base ClearCase 7.0.

      Thanks,
      Rich

        Attachments

          Activity

          Hide
          vlatombe Vincent Latombe added a comment -

          Hi,

          I did a partial fix for version 1.3, but I still get an error at the end of the update. I will need to refine it

          Show
          vlatombe Vincent Latombe added a comment - Hi, I did a partial fix for version 1.3, but I still get an error at the end of the update. I will need to refine it
          Hide
          rsteele rsteele added a comment -

          This still appears to be happening with 1.3.1:

          [png_olr_sep_release] $ cleartool catcs -tag LMDEV1_png_olr_sep_release
          element * CHECKEDOUT
          include \\nawa008\proc\proj\png\2010_sep\png2010_sep_include.csp
          element * /main/LATEST
          load \png\olr
          [LMDEV1_png_olr_sep_release] $ cleartool setcs C:\Hudson\workspace\png_olr_sep_release\configspec4829151664343980146.txt
          cleartool: Error: A snapshot view update is in progress (since 8/25/2010 11:50:08 AM by someone@LMDEV1 (process 2188)).
          cleartool: Error: Unable to set config spec.
          cleartool: Error: Unable to change configuration specification: error detected by ClearCase subsystem.
          FATAL: Base ClearCase failed. exit code=1
          FATAL: java.io.IOException: cleartool did not return the expected exit code. Command line="setcs C:\Hudson\workspace\png_olr_sep_release\configspec4829151664343980146.txt", actual exit code=1

          Show
          rsteele rsteele added a comment - This still appears to be happening with 1.3.1: [png_olr_sep_release] $ cleartool catcs -tag LMDEV1_png_olr_sep_release element * CHECKEDOUT include \\nawa008\proc\proj\png\2010_sep\png2010_sep_include.csp element * /main/LATEST load \png\olr [LMDEV1_png_olr_sep_release] $ cleartool setcs C:\Hudson\workspace\png_olr_sep_release\configspec4829151664343980146.txt cleartool: Error: A snapshot view update is in progress (since 8/25/2010 11:50:08 AM by someone@LMDEV1 (process 2188)). cleartool: Error: Unable to set config spec. cleartool: Error: Unable to change configuration specification: error detected by ClearCase subsystem. FATAL: Base ClearCase failed. exit code=1 FATAL: java.io.IOException: cleartool did not return the expected exit code. Command line="setcs C:\Hudson\workspace\png_olr_sep_release\configspec4829151664343980146.txt", actual exit code=1
          Hide
          rsteele rsteele added a comment -

          See previous comment.

          Show
          rsteele rsteele added a comment - See previous comment.
          Hide
          spolke Szymon Polke added a comment -

          Hi,

          I've proposed a workaround - calling update clears previous one and allows setcs to complete. The problem is update throws IOException itself but it still unlocks clearcase.

          https://github.com/jenkinsci/clearcase-plugin/pull/25

          Show
          spolke Szymon Polke added a comment - Hi, I've proposed a workaround - calling update clears previous one and allows setcs to complete. The problem is update throws IOException itself but it still unlocks clearcase. https://github.com/jenkinsci/clearcase-plugin/pull/25
          Hide
          spolke Szymon Polke added a comment -

          After https://github.com/jenkinsci/clearcase-plugin/commit/1e88ea2a318fc65d8c256d7393a47f2d93366910 the problem is fixed - I've verified that. I think You can close the issue.

          Show
          spolke Szymon Polke added a comment - After https://github.com/jenkinsci/clearcase-plugin/commit/1e88ea2a318fc65d8c256d7393a47f2d93366910 the problem is fixed - I've verified that. I think You can close the issue.

            People

            • Assignee:
              vlatombe Vincent Latombe
              Reporter:
              vlatombe Vincent Latombe
            • Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: