Hello, Given the significant variation in time range that the JBehave test runs, I wouldn't expect the problem to be file size. If it was, it would fail around the same spot. However wanting to investigate all possibilities, I ran a "ulimit -a" and here's what I came up with: core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 106496 max locked memory (kbytes, -l) 32 max memory size (kbytes, -m) unlimited open files (-n) 4096 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 10240 cpu time (seconds, -t) unlimited max user processes (-u) 106496 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited
Earlier in the day, I pulled down the heap dump from the master. Unfortunately it was over 770 megs and I don't have an editor capable of opening a file that large (my laptop is Windows). I'm in the process of requesting some different text editing software. Given the possibility of the heap dump containing confidential information, I'm not posting it to the site. When I'm able to view the output then I'll worry about it. :) -- View this message in context: http://jenkins.361315.n4.nabble.com/Jenkins-exit-code-143-due-to-Unexpected-termination-of-the-channel-tp4652347p4652500.html Sent from the Jenkins users mailing list archive at Nabble.com.
