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

ForkScanner.setHeads raises NoSuchElementException

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • workflow-api-plugin
    • None

      Jenkins 2.107.3, up-to-date plugins, org.jenkins-ci.plugins.workflow:workflow-api:2.27

      I'm seeing exceptions coming from the org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.setHeads method. See the attached file for the stack trace (errors.txt).

      This appears to cause corruption with the stored data, after a restart Jenkins is unable to correctly display the status of the JOB.

       

        1. flowNodeStore.xml.gz
          89 kB
        2. jenkins.log
          536 kB
        3. flowNodeStore-fallback.xml
          12 kB
        4. errors.txt
          37 kB

          [JENKINS-51297] ForkScanner.setHeads raises NoSuchElementException

          bentoi created issue -
          Vivek Pandey made changes -
          Assignee New: Sam Van Oort [ svanoort ]
          jang hyemi (Inactive) made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          bentoi made changes -
          Attachment New: flowNodeStore-fallback.xml [ 43319 ]
          bentoi made changes -
          Attachment New: flowNodeStore-fallback.xml [ 43320 ]
          bentoi made changes -
          Attachment New: jenkins.log [ 43321 ]
          bentoi made changes -
          Attachment New: flowNodeStore.xml.gz [ 43322 ]
          bentoi made changes -
          Attachment Original: flowNodeStore-fallback.xml [ 43320 ]

            svanoort Sam Van Oort
            bentoi bentoi
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: