So we either need to tweak the ulimit settings like this [1] or we
have to figure out what increased the open files amount lately to be
able to reduce it.

[1] 
http://publib.boulder.ibm.com/infocenter/rsahelp/v8/index.jsp?topic=/com.ibm.xtools.installation.rsaws.doc/topics/t_preinst_filehandles.html

On Sat, Feb 4, 2012 at 7:42 PM, Romain Manni-Bucau
<rmannibu...@gmail.com> wrote:
> Yep.
>
> Le 4 févr. 2012 19:39, "dsh" <daniel.hais...@googlemail.com> a écrit :
>
>> Is that on Ubuntu/Linux ?
>>
>> On Sat, Feb 4, 2012 at 7:34 PM, Romain Manni-Bucau
>> <rmannibu...@gmail.com> wrote:
>> > It seems we have an issue with builbot (hemera pby) looking several
>> builds:
>> > too many open file
>> >
>> > - Romain
>> >
>> > Le 4 févr. 2012 19:18, "dsh" <daniel.hais...@googlemail.com> a écrit :
>> >
>> >> Build 1810 [1] seems to be the last good build. If you use the
>> >> waterfall display [2] you are getting more past build results.
>> >>
>> >> [1] http://ci.apache.org/builders/openejb-trunk-ubuntu/builds/1810
>> >> [2] http://ci.apache.org/waterfall?show=openejb-trunk-ubuntu
>> >>
>> >> On Sat, Feb 4, 2012 at 6:38 PM, Alan D. Cabrera <l...@toolazydogs.com>
>> >> wrote:
>> >> > Ahh, I see the emails in commits.  :)
>> >> >
>> >> > Is there any buildbot documentation?  I'm trying to find the last
>> known
>> >> good build.
>> >> >
>> >> >
>> >> > Regards,
>> >> > Alan
>> >> >
>> >> > On Feb 4, 2012, at 8:41 AM, Alan D. Cabrera wrote:
>> >> >
>> >> >> I noticed that we don't seem to get emails on build failures.  Is
>> this
>> >> by plan or do the emails go to another list?
>> >> >>
>> >> >>
>> >> >> Regards,
>> >> >> Alan
>> >> >>
>> >> >> On Jan 31, 2012, at 12:34 PM, David Blevins wrote:
>> >> >>
>> >> >>>
>> >> >>> On Jan 31, 2012, at 11:56 AM, Romain Manni-Bucau wrote:
>> >> >>>
>> >> >>>> we have some buildbot jobs with tests, the main one is
>> >> >>>> http://ci.apache.org/builders/openejb-trunk-ubuntu but we don't
>> have
>> >> access
>> >> >>>> to the output files (junit).
>> >> >>>
>> >> >>> The reports are available.  Some weeks ago I added a "test-results"
>> >> build step that cat's all the reports to stdout so they show up in
>> buildbot:
>> >> >>>
>> >> >>>
>> >>
>> http://ci.apache.org/builders/openejb-trunk-ubuntu/builds/1789/steps/test-results
>> >> >>>
>> >> >>>
>> >> >>> -David
>> >> >>>
>> >> >>>>
>> >> >>>>
>> >> >>>> 2012/1/31 Alan D. Cabrera <l...@toolazydogs.com>
>> >> >>>>
>> >> >>>>>
>> >> >>>>> On Jan 30, 2012, at 9:18 AM, David Blevins wrote:
>> >> >>>>>
>> >> >>>>>>
>> >> >>>>>> On Jan 30, 2012, at 8:22 AM, Alan D. Cabrera wrote:
>> >> >>>>>>
>> >> >>>>>>> I'm getting errors when I try to build trunk:
>> >> >>>>>>>
>> >> >>>>>>>
>> >> >>>>>>> Failed tests:
>> >> >>>>>
>> >>
>> MDB.PojoContextLookup.lookupStatefulBean(org.apache.openejb.test.NumberedTestCase$NamedTest):
>> >> >>>>> Received Exception class
>> >> java.lang.reflect.UndeclaredThrowableException :
>> >> >>>>> null
>> >> >>>>>>>
>> >> >>>>>>> Tests in error:
>> >> >>>>>>> testProxy(org.apache.openejb.core.mdb.JmsProxyTest)
>> >> >>>>>>
>> >> >>>>>> I had that issue this morning too.  I built from a clean m2 repo
>> and
>> >> >>>>> clean checkout and it magically went a away.
>> >> >>>>>>
>> >> >>>>>> Still not sure what the issue might have been.
>> >> >>>>>
>> >> >>>>> Updated and built on a new tower:
>> >> >>>>>
>> >> >>>>> Failed tests:
>> >> >>>>> testValidOpenejbJar(org.apache.openejb.jee.oejb2.OpenejbJarTest):
>> >> >>>>> expected:<...standalone="yes"?>
>> >> >>>>> testConversion(org.apache.openejb.jee.oejb2.ConversionTest): Files
>> >> are
>> >> >>>>> not similar org.custommonkey.xmlunit.DetailedDiff
>> >> >>>>>
>> >> >>>>> Do we have Hudson jobs that test our stuff?  If so, where?  I'd
>> like
>> >> to
>> >> >>>>> review their results.
>> >> >>>>>
>> >> >>>>>> On other notes, welcome back! :)
>> >> >>>>>
>> >> >>>>> Thanks!  The kids have reached a bittersweet milestone where they
>> >> can get
>> >> >>>>> themselves ready for bed.  Daddy hopes to squeeze in some hacking
>> >> then.
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> Regards,
>> >> >>>>> Alan
>> >> >>>>>
>> >> >>>>>
>> >> >>>
>> >> >>
>> >> >
>> >>
>>

Reply via email to