|
The log file shows: Apr 25, 2013 7:03:15 AM jenkins.model.lazy.AbstractLazyLoadRunMap search
WARNING: Assertion error: failing to load #360 EXACT: lo=7,hi=0,size=7,size2=7
java.lang.Exception
at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:441)
at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:526)
at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:379)
at jenkins.model.lazy.AbstractLazyLoadRunMap.newestBuild(AbstractLazyLoadRunMap.java:321)
at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:1059)
at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:142)
at hudson.model.Job.getLastCompletedBuild(Job.java:865)
at sun.reflect.GeneratedMethodAccessor80.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)
at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)
at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)
at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)
at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
There are many exceptions, and while not exactly the same stack trace, it's always an seems to be an "Assertion error" or an "ArrayIndexOutOfBounds" that is the cause, and it almost always seem to be part of in AbstractLazyLoadRunMap.search.
The details (failing to load #360 EXACT: lo=7,hi=0,size=7,size2=7) of the exception are reasonably consistent for both types of exception.
Yesterday, I found a job that was not displaying correctly on the job list of web page. It's "nextBuildNumber" matched (or was off by 1) with the #360 show in the example. I manually set that lower (based on size). I then reload configuration, and the job displayed correctly. The exceptions went away for a few hours, but they came back. Now I notice two jobs not displaying correctly.
This showed up after I upgraded to v.1.512 from 1.450. It also seem to occasionally be killing the executors.
Presumably as a result of the failure, the API is not returning the expected results (I'm getting not finding certain elements that I expect).
|
