Skip to content

[JENKINS-47517] 2.85: StackOverflowError between Queue$Task.getCauseOfBlockage and workflow.job.AfterRestartTask.isBuildBlocked #22374

Closed

Description

@jenkins-infra-bot

Originally reported by jglick, imported from: 2.85: StackOverflowError between Queue$Task.getCauseOfBlockage and workflow.job.AfterRestartTask.isBuildBlocked
  • assignee: jglick
  • status: Resolved
  • priority: Blocker
  • component(s): core
  • label(s): 2.73.3-rejected, pipeline, regression
  • resolution: Fixed
  • resolved: 2017-10-20T22:03:25+00:00
  • votes: 0
  • watchers: 2
  • imported: 2025-11-24

Activity

  1. jenkins-infra-bot commented on Oct 19, 2017

    @jenkins-infra-bot
    Author
  2. jenkins-infra-bot commented on Oct 19, 2017

    @jenkins-infra-bot
    Author
    jglick:
    • Original comment link
    • Raw content of original comment:

      Note: I have not yet checked for the user impact of this bug, e.g. whether it causes ATH failures in WorkflowPluginTest.

    Note: I have not yet checked for the user impact of this bug, e.g. whether it causes ATH failures in WorkflowPluginTest.

  3. jenkins-infra-bot commented on Oct 19, 2017

    @jenkins-infra-bot
    Author
    jglick:
    • Original comment link
    • Raw content of original comment:

      WorkflowPluginTest against 2.85 does print a StackOverflowError at some point, though the test passes anyway.

    WorkflowPluginTest against 2.85 does print a StackOverflowError at some point, though the test passes anyway.

  4. jenkins-infra-bot commented on Oct 19, 2017

    @jenkins-infra-bot
    Author
    jglick:
    • Original comment link
    • Raw content of original comment:

      Does not cause test failure in workflow-job.

    Does not cause test failure in workflow-job.

  5. jenkins-infra-bot commented on Oct 20, 2017

    @jenkins-infra-bot
    Author
    jglick:
    • Original comment link
    • Raw content of original comment:

      Merged toward 2.86.

    Merged toward 2.86.

  6. jenkins-infra-bot commented on Oct 23, 2017

    @jenkins-infra-bot
    Author
    olivergondza:
    • Original comment link
    • Raw content of original comment:

      Not applicable for 2.73 LTS line. As I understand this affects 2.85 only so keeping the candidate flag here to reevaluate in case we pick 2.85 as the next LTS.

    Not applicable for 2.73 LTS line. As I understand this affects 2.85 only so keeping the candidate flag here to reevaluate in case we pick 2.85 as the next LTS.

  7. jenkins-infra-bot commented on Oct 23, 2017

    @jenkins-infra-bot
    Author
    jglick:
    • Original comment link
    • Raw content of original comment:

      Yes this applies only to 2.85.

    Yes this applies only to 2.85.

  8. jenkins-infra-bot commented on Oct 23, 2017

    @jenkins-infra-bot
    Author
    jglick:
    • Original comment link
    • Raw content of original comment:

      Finally happened upon a case where PCT would have caught this: WorkflowTest.demo in workflow-cps passes against 2.84 but fails against 2.85. (And passes against 2.86 with the addition of -Djenkins-test-harness.version=2.31 needed due to JENKINS-47393.)

    Finally happened upon a case where PCT would have caught this: WorkflowTest.demo in workflow-cps passes against 2.84 but fails against 2.85. (And passes against 2.86 with the addition of -Djenkins-test-harness.version=2.31 needed due to JENKINS-47393.)

  9. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    Author

    [Original blocks from Jira: JENKINS-20046]

  10. removed
    bugFor changelog: Minor bug. Will be listed after features
    on Nov 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions