[jbosstools-dev] Red Builds, Yellow Builds & Test Failures (getting ready for Code Freeze TOMORROW)

[Snjezana Peco]

A comandline flag doesn't work in this case. You may want to take a look 
at https://issues.jboss.org/browse/JBIDE-13939

Snjeza

On 4/5/2013 9:00 PM, Nick Boldt wrote:
> Isn't there a commandline flag to suppress that so that the test DOES
> NOT block until timeout?
>
> On 04/05/2013 02:56 PM, Snjezana Peco wrote:
>> Yes, they do.
>>
>> Snjeza
>>
>> On 4/5/2013 8:41 PM, Nick Boldt wrote:
>>> Do the usage tests involve waiting for a user to click the dialog
>>> asking if it's OK to collect anonymous usage stats?
>>>
>>> N
>>>
>>> On 04/05/2013 02:19 PM, Snjezana Peco wrote:
>>>> See https://issues.jboss.org/browse/JBIDE-13939 and
>>>> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBossTools_Trunk/job/jbosstools-base_master/220/console
>>>>
>>>>
>>>>
>>>> The usage tests take 1.02 sec, but freeze.
>>>>
>>>> Snjeza
>>>>
>>>> On 4/3/2013 9:33 PM, Snjezana Peco wrote:
>>>>> I have created JBIDE-13908, JBIDE-13910, JBIDE-13911 and reopened
>>>>> JBIDE-13733. They are related to tests.
>>>>>
>>>>> Snjeza
>>>>>
>>>>> On 4/3/2013 6:30 PM, Nick Boldt wrote:
>>>>>> As code freeze is tomorrow, it's that time of the month where I
>>>>>> have the
>>>>>> pleasure of sending reminder note that if your job is red or yellow,
>>>>>> *you need to fix your tests*.
>>>>>>
>>>>>> Here are today's failures. You'll note that they've all been
>>>>>> failing for
>>>>>> about a week.
>>>>>>
>>>>>> == RED ==
>>>>>>
>>>>>> Base: Failing tests since Mar 24
>>>>>>
>>>>>> Forge: 2 test failures, 8 skipped tests since Mar 24
>>>>>>
>>>>>> Hibernate: COMPILATION FAILURES since ??? (last good build on Feb 18)
>>>>>>
>>>>>> JavaEE: 7 test failures since Mar 31; 11 test failures since Mar 21
>>>>>>
>>>>>> == YELLOW ==
>>>>>>
>>>>>> Central: 1-2 test failures since Apr 1
>>>>>>
>>>>>> JST: 20+ test failures since Mar 28
>>>>>>
>>>>>> Web Services: 917 test failures since Mar 24
>>>>>>