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

[Nick Boldt]

More info here:

https://issues.jboss.org/browse/JBIDE-13939

On 04/05/2013 03:28 PM, � wrote:
> On 04/05/2013 09:00 PM, Nick Boldt wrote:
>> Isn't there a commandline flag to suppress that so that the test DOES
>> NOT block until timeout?
>
> As far as I can say the flag is only suppressing the usage in
> SWTBot-Test where a UI is actually run. The usage test are not running
> UI, thus the flag has no effect on them. Furthermore I can run those
> (even without flag, just by 'mvn clean verify') locally and they run
> perfectly smooth.
>
> [INFO] usage.tests ....................................... SUCCESS [0.004s]
> [INFO] org.jboss.tools.usage.test ........................ SUCCESS
> [10.156s]
>
> There was 0 change in usage since Alpha1 (and even before) so I wonder
> why this should now fail?
> I have to test with Kepler TP though.
>
>
> 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
>>>>>>>
>

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com