Quantcast
Jenkins › Jenkins issues

[JIRA] (JENKINS-15465) Running a maven build on jenkins gives the following log and fails the build NB: htis build was assing before the latest update

classic Classic list List threaded Threaded
♦
♦
 40 messages Options
12
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15465) Running a maven build on jenkins gives the following log and fails the build NB: htis build was assing before the latest update

JIRA noreply@jenkins-ci.org
Issue Type: Bug Bug
Affects Versions: current
Assignee: Unassigned
Components: maven
Created: 10/Oct/12 2:07 PM
Description:

running the build fails with the following error:

ERROR: Processing failed due to a bug in the code. Please report this to [hidden email]
java.lang.NullPointerException
at hudson.tasks.LogRotator.perform(LogRotator.java:119)
at hudson.model.Job.logRotate(Job.java:338)
at hudson.model.Run.execute(Run.java:1581)
at hudson.maven.MavenBuild.access$600(MavenBuild.java:83)
at hudson.maven.MavenBuild$ProxyImpl2.close(MavenBuild.java:545)
at hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:106)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:794)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:589)
at hudson.model.Run.execute(Run.java:1516)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:236)
project=hudson.maven.MavenModuleSet@280d8b87[deploy sdk]
Environment: Ubuntu Linux 2.6 Server x86 GNU/Linux
Project: Jenkins
Labels: jenkins
Priority: Major Major
Reporter: Phumzile Saleni
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15465) Running a maven build on jenkins gives the following log and fails the build NB: htis build was assing before the latest update

JIRA noreply@jenkins-ci.org

We're facing the same issue after upgrading to 1.485. Seems like all our builds now fail with this error.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15465) Running a maven build on jenkins gives the following log and fails the build NB: this build was working before the latest update

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Change By: Phumzile Saleni (10/Oct/12 3:17 PM)
Summary: Running a maven build on jenkins gives the following log and fails the build NB:  htis  this  build was  assing  working  before the latest update
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15465) Running a maven build on jenkins gives the following log and fails the build NB: this build was working before the latest update

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
core/src/main/java/hudson/model/RunMap.java
core/src/main/java/hudson/util/RunList.java
http://jenkins-ci.org/commit/jenkins/807dc7174cd8ed4ec3cb9562f1c3f90f4035cf33
Log:
JENKINS-15465 tweaking subList implementation and iterator.

I can't really think of how null ends up in the resulting list, but adding a check in Iterator to detect that situation.

Also, improved the efficiency of the subList implementation.

Compare: https://github.com/jenkinsci/jenkins/compare/35eadbcf6e96...807dc7174cd8
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15465) RunList returning null from its elements in 1.485

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

Updating the title to better represent what this is about.
Change By: Kohsuke Kawaguchi (10/Oct/12 5:12 PM)
Summary: Running a maven build on jenkins gives the following log and fails the build NB: this build was working before the latest update RunList returning null from its elements in 1.485
Assignee: Kohsuke Kawaguchi
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15465) RunList returning null from its elements in 1.485

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

Excellent - thanks! I just finished compiling Jenkins, in an attempt to fix it myself.

Will there be a release soon, considering that this is a showstopper for many, or should people needing it right away compile their own version? Since this is an bundled plugin, updating jenkins.war should be enough I guess?

(The RC-link http://mirrors.jenkins-ci.org/war-rc/latest/jenkins.war currently shows 404)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15465) RunList returning null from its elements in 1.485

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
dogfood commented on Bug JENKINS-15465

Integrated in jenkins_main_trunk #1987
JENKINS-15465 tweaking subList implementation and iterator. (Revision 807dc7174cd8ed4ec3cb9562f1c3f90f4035cf33)

Result = UNSTABLE
kohsuke : 807dc7174cd8ed4ec3cb9562f1c3f90f4035cf33
Files :

  • core/src/main/java/hudson/util/RunList.java
  • core/src/main/java/hudson/model/RunMap.java
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15465) RunList returning null from its elements in 1.485

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Change By: Kohsuke Kawaguchi (10/Oct/12 6:20 PM)
Component/s: core
Component/s: maven
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15465) RunList returning null from its elements in 1.485

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

Those who are seeing this issue, can you please try build #1987 or later and report what happens?

This is a very critical bug that I'd like to fix quickly, so I really appreciate everyone's help.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15465) RunList returning null from its elements in 1.485

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

I'm not seeing the exact same symptoms as reported here but I'm guessing its the same. I'm getting an NPE in hudson.util.RunList$1.compare

0-Oct-2012 21:13:36 hudson.ExpressionFactory2$JexlExpression evaluate
WARNING: Caught exception evaluating: empty(entries). Reason: java.lang.NullPointerException
java.lang.NullPointerException
        at hudson.util.RunList$1.compare(RunList.java:87)
        at hudson.util.RunList$1.compare(RunList.java:85)
        at com.google.common.collect.Iterators$MergingIterator$1.compare(Iterators.java:1300)
        at com.google.common.collect.Iterators$MergingIterator$1.compare(Iterators.java:1297)
...

Downloading build 1989 jenkins.war now.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15465) RunList returning null from its elements in 1.485

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

On startup I'm getting the following assertion failures.

10-Oct-2012 23:12:26 jenkins.model.lazy.AbstractLazyLoadRunMap search
WARNING: Assertion error: failing to load #2147483647 DESC: lo=18,hi=22,pivot=20,size=21 (initial:lo=0,hi=22)
java.lang.Exception
        at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:414)
        at jenkins.model.lazy.AbstractLazyLoadRunMap.newestBuild(AbstractLazyLoadRunMap.java:293)
        at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:998)
        at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:184)
        at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:665)
        at hudson.maven.MavenModule.updateTransientActions(MavenModule.java:411)
        at hudson.model.AbstractProject.onLoad(AbstractProject.java:299)
        at hudson.maven.MavenModule.onLoad(MavenModule.java:236)
        at hudson.model.Items.load(Items.java:221)
        at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:99)
        at hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:669)
        at hudson.model.Items.load(Items.java:221)
        at jenkins.model.Jenkins$17.run(Jenkins.java:2507)
        at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
        at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
        at jenkins.model.Jenkins$7.runTask(Jenkins.java:883)
        at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
        at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
        at java.lang.Thread.run(Thread.java:679)
10-Oct-2012 23:12:26 jenkins.InitReactorRunner$1 onTaskFailed
SEVERE: Failed Loading job tcserv
java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #2147483647 DESC: lo=18,hi=22,pivot=20,size=21 (initial:lo=0,hi=22)
        at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:415)
        at jenkins.model.lazy.AbstractLazyLoadRunMap.newestBuild(AbstractLazyLoadRunMap.java:293)
        at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:998)
        at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:184)
        at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:665)
        at hudson.maven.MavenModule.updateTransientActions(MavenModule.java:411)
        at hudson.model.AbstractProject.onLoad(AbstractProject.java:299)
        at hudson.maven.MavenModule.onLoad(MavenModule.java:236)
        at hudson.model.Items.load(Items.java:221)
        at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:99)
        at hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:669)
        at hudson.model.Items.load(Items.java:221)
        at jenkins.model.Jenkins$17.run(Jenkins.java:2507)
        at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
        at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
        at jenkins.model.Jenkins$7.runTask(Jenkins.java:883)
        at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
        at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
        at java.lang.Thread.run(Thread.java:679)
10-Oct-2012 23:12:26 jenkins.InitReactorRunner$1 onAttained
INFO: Loaded all jobs
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15465) RunList returning null from its elements in 1.485

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

Now reproduced with a local build of jenkins.war.

This issue only seems to crop up on about 1 in 3 startups of jenkins.

I got a couple more assertion failures with the current set of information on it.

WARNING: Assertion error: failing to load #2147483647 DESC: lo=12,hi=22,pivot=17,size=21 (initial:lo=0,hi=22,size=22)

It looks like the size of the array is shrinking from 22 to 21 during loading.

Looking at my builds directory I only have 21 builds in there.

richm@royalcounty:~$ ls /opt/hudson/jobs/tcserv/builds/
1241/                1255/                2012-10-08_13-01-06/
1242/                1256/                2012-10-08_22-01-06/
1243/                1257/                2012-10-09_01-01-06/
1244/                1258/                2012-10-09_14-41-42/
1245/                1259/                2012-10-09_16-01-06/
1246/                1260/                2012-10-10_15-01-06/
1247/                2012-05-03_19-38-34/ 2012-10-10_16-01-06/
1248/                2012-10-05_01-01-06/ 2012-10-10_17-01-06/
1249/                2012-10-05_02-01-06/ 2012-10-10_18-01-06/
1250/                2012-10-05_11-01-06/ 2012-10-10_18-15-41/
1251/                2012-10-05_14-01-06/ 2012-10-10_18-41-13/
1252/                2012-10-05_14-28-04/ 2012-10-10_19-10-01/
1253/                2012-10-05_15-01-06/ 2012-10-10_21-00-57/
1254/                2012-10-05_16-01-06/ 990/
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15465) RunList returning null from its elements in 1.485

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

Confirmed that I am seeing NPE's being thrown on M2 jobs with up/downstream dependencies. Standalone jobs with Maven build steps do not have this issue.

I'm not seeing any data loss in any of my M2 jobs.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15465) RunList returning null from its elements in 1.485

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

I just deployed build 1990 and the issue appears to have been resolved. I am no longer seeing NPE's on M2 jobs with up/downstream dependencies.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15465) RunList returning null from its elements in 1.485

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

It looks to me like the additional builds in the list are due to maven submodule builds where the top level build record no longer exists. I added debug into the removal codepath where it detects a null r value and the ones it is removing correspond to build records that only exist at the lower level

11-Oct-2012 01:21:42 jenkins.model.lazy.AbstractLazyLoadRunMap search
WARNING: r was null for pivot=0, id=2010-10-28_01-01-34
richm@royalcounty:~$ find /opt/hudson/jobs/tcserv -name 2010-10-28_01-01-34
/opt/hudson/jobs/tcserv/modules/a.b.c$m1/builds/2010-10-28_01-01-34
/opt/hudson/jobs/tcserv/modules/a.b.c$m2/builds/2010-10-28_01-01-34
/opt/hudson/jobs/tcserv/modules/a.b.c$m3/builds/2010-10-28_01-01-34
/opt/hudson/jobs/tcserv/modules/a.b.c$m4/builds/2010-10-28_01-01-34
/opt/hudson/jobs/tcserv/modules/a.b.c$m5/builds/2010-10-28_01-01-34
/opt/hudson/jobs/tcserv/modules/a.b.c$m6/builds/2010-10-28_01-01-34
/opt/hudson/jobs/tcserv/modules/a.b.c$m7/builds/2010-10-28_01-01-34
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15465) RunList returning null from its elements in 1.485

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

See JENKINS-15439 for what I suspect will fix the issue.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15465) RunList returning null from its elements in 1.485

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

I've just started testing build 1990, and I am not sure what my status is:

After 15 minutes of uptime I have ~180MB of log files, apparently full of exceptions like this:

[#|2012-10-11T09:22:11.437+0200|WARNING|sun-appserver2.1|hudson.util.RobustCollectionConverter|_ThreadID=17;_ThreadName=Loading job Insights Oberon Oracle Tests;_RequestID=1a7ebc56-d6cb-4557-b695-a3755c692961;|Failed to resolve class
com.thoughtworks.xstream.mapper.CannotResolveClassException: org.jvnet.hudson.plugins.DownstreamBuildViewAction : org.jvnet.hudson.plugins.DownstreamBuildViewAction
at com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:68)

All jobs have been loaded, as far as I can see, and builds now seem to complete.

But: When I go to jenkins/administrativeMonitor/OldData/manage I sometimes get an exception (manage.jelly:35:59: <j:forEach> java.util.ConcurrentModificationException) and whenever the page loads I see plenty of jobs that weren't loaded due to CannotResolveClassException: org.jvnet.hudson.plugins.DownstreamBuildViewAction: org.jvnet.hudson.plugins.DownstreamBuildViewAction
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15465) RunList returning null from its elements in 1.485

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

Update: Plenty of historical builds are now missing (all builds for several jobs), and I am pretty sure those jobs were present when I started writing my previous comment...

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15465) RunList returning null from its elements in 1.485

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

Yes, build history is missing with 1.485. Going back to 1.484 brings the history back.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15465) RunList returning null from its elements in 1.485

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

The fix that I proposed for JENKINS-15439 does not fully fix the issue. It fixes the issue with AbstractLazyLoadRunMap search failing but I still see some null values in RunList.

The null values are not present when Jenkins starts up but after a while (an hour or two) then the null values are present.

In my case I have worked out that I can cause a symptom of the error to occur by reading the rssAll feed. Immediately after jenkins starts up this reads normally but when things have gone wrong the feed returns the error.

A simple

wget -O /tmp/rssAll.xml http://localhost:8080/jenkins/rssAll

Will force the error.

Stacktrace as follows.

Caused by: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.487-SNAPSHOT.jar!/hudson/atom.jelly:48:44: <j:forEach> java.lang.NullPointerException
        at org.kohsuke.stapler.jelly.JellyRequestDispatcher.forward(JellyRequestDispatcher.java:60)
        at hudson.model.RSS.forwardToRss(RSS.java:86)
        at hudson.model.View.rss(View.java:957)
        at hudson.model.View.doRssAll(View.java:941)
        ... 69 more

I added some debug into the RunList constructor that gets called in the doRssAll method. That gives me approximately 500 null entries in the constructed RunList. All of these are maven submodule entries. At this moment I am not sure if it is every submodule entry (with a build record) that is null but that is certainly a close approximation.

11-Oct-2012 13:18:21 hudson.util.RunList oldelvetCheckRunList
WARNING: Assertion error: null runlist entry for job=a.b.c.d:mod1
11-Oct-2012 13:18:21 hudson.util.RunList oldelvetCheckRunList
WARNING: Assertion error: null runlist entry for job=a.b.c.d:mod1
11-Oct-2012 13:18:21 hudson.util.RunList oldelvetCheckRunList
WARNING: Assertion error: null runlist entry for job=a.b.c.d:mod2
11-Oct-2012 13:18:22 hudson.util.RunList oldelvetCheckRunList
WARNING: Assertion error: null runlist entry for job=a.b.c.d:mod3
11-Oct-2012 13:18:22 hudson.util.RunList oldelvetCheckRunList
WARNING: Assertion error: null runlist entry for job=a.b.c.d:mod3
11-Oct-2012 13:18:22 hudson.util.RunList oldelvetCheckRunList
WARNING: Assertion error: null runlist entry for job=a.b.c.d:mod3
11-Oct-2012 13:18:22 hudson.util.RunList oldelvetCheckRunList
WARNING: Assertion error: null runlist entry for job=a.b.c.d:mod3
11-Oct-2012 13:18:22 hudson.util.RunList oldelvetCheckRunList
WARNING: Assertion error: null runlist entry for job=a.b.c.d:mod3
11-Oct-2012 13:18:22 hudson.util.RunList oldelvetCheckRunList
WARNING: Assertion error: null runlist entry for job=a.b.c.d:mod4
11-Oct-2012 13:18:22 hudson.util.RunList oldelvetCheckRunList
WARNING: Assertion error: null runlist entry for job=a.b.c.d:mod5
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12
Loading...
Powered by Nabble Edit this page