[JIRA] (JENKINS-58439) Repo plugin - java.lang.StackOverflowError (getLastState issue)

2 views
Skip to first unread message

tomasz.dudala@nsn.com (JIRA)

unread,
Jul 11, 2019, 5:48:02 AM7/11/19
to jenkinsc...@googlegroups.com
tdudala created an issue
 
Jenkins / Bug JENKINS-58439
Repo plugin - java.lang.StackOverflowError (getLastState issue)
Issue Type: Bug Bug
Assignee: Unassigned
Components: pipeline, repo-plugin
Created: 2019-07-11 09:47
Environment: org.jenkins-ci.plugins:repo:1.10.7
Jenkins ver. 2.174
Labels: repo pipeline stackoverflow getLastState
Priority: Critical Critical
Reporter: tdudala

Use case:

Start job (creates repo tool snapshot.xml from current state)
    |
    Worker job
         |_ Build stage1
         |_ Build stage2
         |_ Build stage3

Start job uses SCM (gerrit repo) polling mechanism (freestyle job)
Worker job is pipeline job which takes snapshot as an input from "Start job"
Snapshot is passed to worker build stages which are run paralelly
Every build stage contains of activities:

  • assign dedicated node with clean workspace (node always have only one executor available, it's not possible to run parallel builds on this node)
  • launch repo tool:
  • init using snapshot
  • repo sync
    Until now everything works properly, then.. some repo plugin methods are executed resulting witt error:

13:38:36 java.lang.StackOverflowError
13:38:36 at hudson.model.Actionable.getAction(Actionable.java:330)
13:38:36 at hudson.plugins.repo.RepoScm.getLastState(RepoScm.java:900)
13:38:36 at hudson.plugins.repo.RepoScm.getLastState(RepoScm.java:907)
13:38:36 at hudson.plugins.repo.RepoScm.getLastState(RepoScm.java:907)
13:38:36 at hudson.plugins.repo.RepoScm.getLastState(RepoScm.java:907)
13:38:36 at hudson.plugins.repo.RepoScm.getLastState(RepoScm.java:907)
13:38:36 at hudson.plugins.repo.RepoScm.getLastState(RepoScm.java:907)
13:38:36 at hudson.plugins.repo.RepoScm.getLastState(RepoScm.java:907)
13:38:36 at hudson.plugins.repo.RepoScm.getLastState(RepoScm.java:907)
...

It seems that it can't get needed information and it happens occasionally.
I observe that problems occurs more often if more parallel build stages are run.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
Reply all
Reply to author
Forward
0 new messages