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

AssertionError: "Releasing unallocated workspace"

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • core
    • None
    • Platform: All, OS: Linux

      FATAL: Releasing unallocated workspace /hudson/workspaces/TRUNK-PATCH
      java.lang.AssertionError: Releasing unallocated workspace
      /hudson/workspaces/TRUNK-PATCH
      at hudson.slaves.WorkspaceList.release(WorkspaceList.java:74)
      at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:365)
      at hudson.model.Run.run(Run.java:1090)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
      at hudson.model.ResourceController.execute(ResourceController.java:93)
      at hudson.model.Executor.run(Executor.java:122)

          [JENKINS-4206] AssertionError: "Releasing unallocated workspace"

          sberlotto created issue -

              • Issue 4210 has been marked as a duplicate of this issue. ***

          Kohsuke Kawaguchi added a comment - Issue 4210 has been marked as a duplicate of this issue. ***
          Kohsuke Kawaguchi made changes -
          Link New: This issue is duplicated by JENKINS-4210 [ JENKINS-4210 ]

          Changing summary to attract attention for others who see the same problem.

          Kohsuke Kawaguchi added a comment - Changing summary to attract attention for others who see the same problem.
          Kohsuke Kawaguchi made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          I'm so far failing to reproduce this issue on my Hudson, so I need help from
          people seeing this problem.

          1. Does this problem happen reliably every time, or randomly/sporadically?

          2. If you can share the config.xml of the job that sees this problem, please
          attach it here. You can mask the contents of the shell script and other
          sensitive information, but it helps me if I know what
          builder/publisher/trigger/etc are enabled, as well as the kind of SCM.

          3. Tell me about your master/slave environment. How many executors do you have,
          how/if your jobs are tied?

          Kohsuke Kawaguchi added a comment - I'm so far failing to reproduce this issue on my Hudson, so I need help from people seeing this problem. 1. Does this problem happen reliably every time, or randomly/sporadically? 2. If you can share the config.xml of the job that sees this problem, please attach it here. You can mask the contents of the shell script and other sensitive information, but it helps me if I know what builder/publisher/trigger/etc are enabled, as well as the kind of SCM. 3. Tell me about your master/slave environment. How many executors do you have, how/if your jobs are tied?

          Oh, could it be that this happens only with the use of "custom workspace"?

          Kohsuke Kawaguchi added a comment - Oh, could it be that this happens only with the use of "custom workspace"?

              • Issue 4182 has been marked as a duplicate of this issue. ***

          Kohsuke Kawaguchi added a comment - Issue 4182 has been marked as a duplicate of this issue. ***
          Kohsuke Kawaguchi made changes -
          Link New: This issue is duplicated by JENKINS-4182 [ JENKINS-4182 ]

          sberlotto added a comment -

          Created an attachment (id=838)
          config os job

          sberlotto added a comment - Created an attachment (id=838) config os job

            Unassigned Unassigned
            sberlotto sberlotto
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: