[
https://issues.apache.org/jira/browse/BUILDS-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137681#comment-14137681
]
Patrick Hunt commented on BUILDS-17:
------------------------------------
[~gkesavan] that's not what we're seeing in the job. Is this the same host
(H3)? (I don't know the names). here's what we see
{noformat}
Building remotely on H3 (Mapreduce Hadoop Zookeeper Hdfs) in workspace
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build
Reverting /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk
to depth infinity with ignoreExternals: false
Updating http://svn.apache.org/repos/asf/zookeeper/trunk at revision
'2014-09-16T20:01:00.662 +0000'
At revision 1625366
no change for http://svn.apache.org/repos/asf/zookeeper/trunk since the
previous build
No emails were triggered.
[PreCommit-ZOOKEEPER-Build] $ /bin/bash /tmp/hudson3167634542373095077.sh
/home/jenkins/tools/java/latest1.6/bin/java
java version "1.6.0_45"
Java(TM) SE Runtime Environment (build 1.6.0_45-b06)
Java HotSpot(TM) Server VM (build 20.45-b01, mixed mode)
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 386178
max locked memory (kbytes, -l) 64
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) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 386178
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
Buildfile:
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml
{noformat}
https://builds.apache.org/view/S-Z/view/ZooKeeper/job/PreCommit-ZOOKEEPER-Build/2342/
[~abayer] any insight re the jenkins setup? Perhaps related to how the job is
run?
> ulimit set too low on some jenkins build hosts
> ----------------------------------------------
>
> Key: BUILDS-17
> URL: https://issues.apache.org/jira/browse/BUILDS-17
> Project: Infra Build Platform
> Issue Type: Bug
> Components: Jenkins
> Reporter: Patrick Hunt
> Assignee: Giridharan Kesavan
> Priority: Blocker
>
> Our precommit job is failing, this started just after the recent major
> upgrades to the jenkins infra (was fine prior to that):
> https://builds.apache.org/view/S-Z/view/ZooKeeper/job/PreCommit-ZOOKEEPER-Build/2303/
> The test is still failing with the same error (too many open
> files) and afaict the ulimit is still just set to 4k. I'm printing the
> ulimit info at the start of the job, here it is:
> core file size (blocks, -c) 0
> data seg size (kbytes, -d) unlimited
> scheduling priority (-e) 0
> file size (blocks, -f) unlimited
> pending signals (-i) 386177
> max locked memory (kbytes, -l) 64
> 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) 8192
> cpu time (seconds, -t) unlimited
> max user processes (-u) 386177
> Please increase the ulimit to a significantly larger value (perhaps you can
> set it to what it was set to prior to the upgrade?)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
