I've never heard a SEGKILL on timeout for maven (as can be seen from (code
137) sent to build task), but have seen this a few times when a server
continuously fails to keep the correct time and NTP updates the time.

Check if the server is loosing time and has the NTP running where on the
update there is a big time difference and JVM exits. The easy solutions is
to shutdown NTP and let it give wrong timestamps or better if server
hardware needs to be fixed.

---
Regards,
Saptarshi PURKAYASTHA

My Tech Blog:  http://sunnytalkstech.blogspot.com
You Live by CHOICE, Not by CHANCE


On 26 August 2011 17:20, Ben Wolfe <[email protected]> wrote:

> This happened a long while ago too.  I thought it was bamboo killing it at
> the time due to lack of memory for its instance, but I'm not sure.  Its
> being killed after different tests each time and on different builds, so I
> hesitate to think its a test timing out.  Its also happening fairly early on
> some  runs, so its not an overall timeout.
>
> Ben
>
>
> On Fri, Aug 26, 2011 at 2:43 PM, Michael Downey <[email protected]>wrote:
>
>> Hi there,
>>
>> On Fri, Aug 26, 2011 at 3:26 AM, Ben Wolfe <[email protected]> wrote:
>>
>>>
>>> Michael, CI has failed 10+ times in the last week due to non-code
>>> issues.  All failed builds have been "killed" by something or someone while
>>> running at different points of the compilation.
>>>
>>> build       26-Aug-2011 03:16:25    Running 
>>> org.openmrs.api.EncounterServiceTest
>>> build       26-Aug-2011 03:16:29    Killed
>>>
>>> Is there a root cause?  Or a solution?
>>>
>>
>> I'm not sure if you were in the chat at the time but it's actually Maven
>> killing the tests, not Bamboo. My initial research suggested that one or
>> more tests were exceeding their timeout value. Do you have any ideas about
>> how we can instrument this to see what specifically is failing/timing
>> out/etc.? I suppose we could just turn up verbosity on maven for a while
>> perhaps?
>>
>> Has anyone else run into this scenario with Maven in the past? Any
>> thoughts or ideas?
>>
>> -Michael
>>
>
>

_________________________________________

To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to 
[email protected] with "SIGNOFF openmrs-devel-l" in the  body (not 
the subject) of your e-mail.

[mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]

Reply via email to