[jbosstools-dev] Please take care of CI job for your component!

[Denis Golovin]

It seems to be fine now, at least common build is not failing anymore.

Denis

On 08/31/2012 12:10 AM, Max Rydahl Andersen wrote:
> have this change been done on our jenkins instance ?
>
> /max
>
> On 30 Aug 2012, at 23:28, Denis Golovin <dgolovin at exadel.com> wrote:
>
>> That's what I found. The problem is in vncserver. Latest vnc in
>> combination with gnome manager makes tests waiting forever in UI thread
>> when importing projects and use JobMtils.waitForIdle(). It turned out to
>> make the tests move ahead I needed to open vnc display in viewer and
>> sent any event from keyboard of from mouse.
>>
>> the fix was replacing in ~/.vnc/xstartup
>>
>> gnome-session &
>>
>> to
>>
>> metacity --replace &
>>
>> and tests are fine again.
>>
>> I'm not sure but that might be the case.
>>
>> Denis
>>
>> On 08/30/2012 01:04 PM, Nick Boldt wrote:
>>> Not sure... you tell me:
>>>
>>> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-3.3_stable_branch.component--cdi/buildTimeTrend
>>> (3.3.x branch)
>>>
>>> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-3.3_trunk.component--cdi/buildTimeTrend
>>> (trunk)
>>>
>>>
>>> On 08/30/2012 03:02 PM, Alexey Kazakov wrote:
>>>> On 08/30/2012 11:41 AM, Nick Boldt wrote:
>>>>> If you spread the 25 components out in approximate order, assuming
>>>>> that no two run in parallel (which is of course not the case but makes
>>>>> it easier to estimate times) then a fresh CDI build is over 9 hours
>>>>> after a fresh usage, tests, or common build. Since CDI has over an
>>>>> hour of tests in it, Seam is therefore close to 12 hours down the stack.
>>>> An hour for CDI tests? Why so long? It takes ~ 11 minutes (about 1000
>>>> JUnit tests) with Tycho on my laptop.
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev