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 <[email protected]>
>> 
>>> 
>>> 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