Katherine Marsden <[email protected]> writes: > On 4/7/2013 8:16 PM, Apache Jenkins Server wrote: > > The reason for this failure seems to be: > > "Build timed out (after 120 minutes). Marking the build as failed." > > but it did seem to continue and I don't see where it says whether the > tests actually passed or failed.
Actually, it looks like it did get killed before it had completed: https://builds.apache.org/job/Derby-10.9-derbyall/57/console The last test was lang/triggerBeforeTrig.sql, and in a full test run there should be many tests running after it. According to the above link, just building the jars took 42 minutes, so this slave must have been extremely slow today. > If I run derbyall on 10.9 in my > client it all passes. I guess I will just wait and see if it corrects > itself. I've triggered a rerun manually. If it keeps happening, we'll have to consider upping the timeout. -- Knut Anders
