Jenkins job failure analysis

[Sameer Khan]

My bad! Thanks for correcting me!

Mark, 

In my case the build does go thru if re-built at times. Also when the machine was upgraded such failures are not observed.

Thanks,

Sameer

On 20-Aug-2019, at 17:49, Mark Waite <mark.ea...@gmail.com> wrote:

This is a question best asked on the user mailing list.  The developer list is used for development discussions related to Jenkins and its components (plugins, modules, etc.).

Jenkins executes processes (junit tests, for example) and reports the return value of those processes and optionally analyzes the results of those processes to decide the state of the job.  If a process returns a non-zero exit code, that will generally cause Jenkins to mark the job as failed.  If a junit process writes a report file that Jenkins analyzes and that file includes a failing test, that will generally cause Jenkins to mark the job as unstable.

On Tue, Aug 20, 2019 at 2:53 AM Sameer <sameer...@gmail.com> wrote:

Hi,

I have been building my Java application using Jenkins (ver. 2.187) which was running in an EC2 instance. My code has Junit tests also. However sometimes the job fails for no reason valid to the code. Once the EC2 instance was upgraded with better resources it started working smoothly. Is there way, I could find the root cause of failure in such a case? Basically I want to understand at Jenkins level what made it to fail the job.

Any pointers would be appreciated!

Thanks,

Sameer

-- 
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3867ea26-146f-4a32-84b3-08952c695f1a%40googlegroups.com.

-- 

Thanks!

Mark Waite

-- 
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/jMQm4d1tcsg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtHDLL5WvuBpRXtqbDRtBuUB2yGB%2BUd%2BRJcZt0wobTs_ow%40mail.gmail.com.

[Sameer Khan]

My bad! Thanks for correcting me!

Mark, in my case the build does go thru if re-built at times. Also when the machine was upgraded such failures are not observed.

[Mark Waite]

If resource use on the "strained" machine decreased just enough to allow the executed process to succeed, then Jenkins would report the job was a success.  If resource use on the "strained" machine increased just enough to cause the Linux kernel to kill the process or just enough to cause some other overload condition to kill the process, then Jenkins would report the job failed.

Overload conditions (high memory use, disc full, etc.) are common sources of variability.  If that variability is unintentional, then it is best to resolve the overload condition as you did.  Add capacity and allow the tests to run with enough resources.

You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1B30EB95-70BF-44E7-8445-0301EEFD369E%40gmail.com.

--

Thanks!

Mark Waite