On Wed, Mar 16, 2011 at 10:55 AM, Kristian Waagan <[email protected]> wrote: > Den 16.03.2011 17:55, skrev Kathey Marsden: >> >> On 3/15/2011 7:46 PM, Kathey Marsden wrote: >>> >>> On 3/15/2011 7:09 PM, Apache Hudson Server wrote: >>>> >>>> buildjars: >>>> >>>> BUILD SUCCESSFUL >>>> Total time: 1 minute 31 seconds >>>> [WARNINGS] Parsing warnings in console log... >>>> [WARNINGS] JavaDoc : Found 0 warnings. >>>> ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due >>>> to exception >>>> java.lang.ClassCastException: cannot assign instance of hudson.FilePath >>>> to field hudson.plugins.analysis.core.ParserResult$FilePathAdapter.wrapped >>>> of type hudson.FilePath in instance of >>>> hudson.plugins.analysis.core.ParserResult$FilePathAdapter >>>> at >>>> java.io.ObjectStreamClass$FieldReflector.setObjFieldValues(ObjectStreamClass.java:2056) >>>> at >>>> java.io.ObjectStreamClass.setObjFieldValues(ObjectStreamClass.java:1229) >>>> at >>>> java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1969) >>>> at >>>> java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1887) >>>> at >>>> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1770) >>>> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1346) >>>> at >>>> java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1963) >>>> at >>>> java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1887) >>>> at >>>> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1770) >>>> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1346) >>>> at >>>> java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1963) >>>> at >>>> java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1887) >>>> at >>>> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1770) >>>> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1346) >>>> at >>>> java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1963) >>>> at >>>> java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1887) >>>> at >>>> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1770) >>>> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1346) >>>> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368) >>>> at hudson.remoting.UserRequest.deserialize(UserRequest.java:178) >>>> at hudson.remoting.UserRequest.perform(UserRequest.java:98) >>>> at hudson.remoting.UserRequest.perform(UserRequest.java:48) >>>> at hudson.remoting.Request$2.run(Request.java:270) >>>> at >>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) >>>> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) >>>> at java.util.concurrent.FutureTask.run(FutureTask.java:166) >>>> 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:636) >>>> >>> I am not actually sure what this error means and what to do about it. I >>> am hoping it is some sort of transient Hudson/Jenkins issue as the derby >>> build itself seemed to complete successfully. Does anyone have any ideas? >>> >> Happily the nightlies and tinderbox do not seem to be affected by this >> problem, so I think I will go ahead and check the DERBY-4907 fix into 10.5. >> If anyone has any information on how to report this problem or do something >> about it, let me know. I saw this thread from March 8 indicating similar, >> but not the exact same problem. >> >> http://old.nabble.com/Build-failed-in-Jenkins%3A-Derby-trunk--798-ts31100060.html#a31100879 >> >> >> Kathey >> > > Hi all, > > This is a problem that surfaced when ASF infra upgraded Hudson to Jenkins. > It has been reported as http://issues.jenkins-ci.org/browse/JENKINS-9017. > Very annoying that this happens now this close to a release. Shall we simply > ignore these failures, or disable the Derby build job until the intermittent > issue has been addressed? > > As already mentioned, the tinderbox should pick up if the build is broken by > a commit. > > > -- > Kristian >
I'd say leave things as is for now, as long as we can say it's this problem. We may need to pay a bit closer attention to the details of the failure, in this case, the "BUILD SUCCESSFULL", and "[WARNINGS] JavaDoc : Found 0 warnings" suggested there wasn't a serious derby issue. We can reassess if the intermittent occurrence becomes more permanent and/or irritating. Myrna
