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

jenkins.security.Security218Test#jnlpSlave is flaky

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • None
    • 2.383

      jenkins.security.Security218Test#jnlpSlave fails not infrequently on Windows as in e.g. this run. I suspect this is due to the split of instance-identity. Based on the logs of that run and other similar runs, Jenkins#getAgentProtocols must be returning the empty set, and I suspect the reason why is that the initialization of JnlpSlaveAgentProtocol4 (which depends on instance-identity having been initialized) is racing with the initialization of instance-identity. Our Windows test agents are very slow, so the problem can probably be reproduced by adding a sleep statement somewhere.

          [JENKINS-70206] jenkins.security.Security218Test#jnlpSlave is flaky

          Basil Crow created issue -
          Vandit Singh made changes -
          Assignee New: Vandit Singh [ vandit1604 ]
          Jesse Glick made changes -
          Assignee Original: Vandit Singh [ vandit1604 ] New: Jesse Glick [ jglick ]
          Jesse Glick made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Jesse Glick made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]
          Jesse Glick made changes -
          Link New: This issue is caused by JENKINS-55582 [ JENKINS-55582 ]
          Jesse Glick made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Review [ 10005 ] New: Fixed but Unreleased [ 10203 ]
          Jesse Glick made changes -
          Remote Link New: This issue links to "jenkins #7514 (Web Link)" [ 28395 ]
          Basil Crow made changes -
          Released As New: 2.383
          Status Original: Fixed but Unreleased [ 10203 ] New: Closed [ 6 ]

            jglick Jesse Glick
            basil Basil Crow
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: