See <https://builds.apache.org/job/HBase-0.98/526/changes>
Changes: [stack] HBASE-12021 Hbase shell does not respect the HBASE_OPTS set by the user in console (Ashish Singhi) [larsh] HBASE-12023 HRegion.applyFamilyMapToMemstore creates too many iterator objects. (Vladimir Rodionov) [larsh] HBASE-12023 addendum ------------------------------------------ Started by an SCM change Building remotely on jenkins-ubuntu-1404-4gb-5fa (jenkins-cloud-4GB Ubuntu ubuntu) in workspace <https://builds.apache.org/job/HBase-0.98/ws/> Cloning the remote Git repository Cloning repository https://git-wip-us.apache.org/repos/asf/hbase.git > git init <https://builds.apache.org/job/HBase-0.98/ws/> Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/hbase.git > git --version > git fetch --tags --progress > https://git-wip-us.apache.org/repos/asf/hbase.git > +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url > https://git-wip-us.apache.org/repos/asf/hbase.git > git config remote.origin.fetch +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url > https://git-wip-us.apache.org/repos/asf/hbase.git Cleaning workspace > git rev-parse --verify HEAD No valid HEAD. Skipping the resetting > git clean -fdx Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/hbase.git > git fetch --tags --progress > https://git-wip-us.apache.org/repos/asf/hbase.git > +refs/heads/*:refs/remotes/origin/* > git rev-parse origin/0.98^{commit} Checking out Revision 371ad2803d12757ead97d32bdc83154ebcb3f086 (origin/0.98) > git config core.sparsecheckout > git checkout -f 371ad2803d12757ead97d32bdc83154ebcb3f086 > git rev-list f3e8140f84d36f7a11be73636793f1270d19b4e4 [HBase-0.98] $ /bin/bash -xe /tmp/hudson6578016636381822728.sh + ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 31591 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 60000 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) 10240 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited + rm -rf /tmp/hbase-jenkins/hbase + ls /home/hudson/tools ls: cannot access /home/hudson/tools: No such file or directory Build step 'Execute shell' marked build as failure Performing Post build task... Match found for :.* : True Logical operation result is TRUE Running script : ZOMBIE_TESTS_COUNT=`jps | grep surefirebooter | wc -l` if [[ $ZOMBIE_TESTS_COUNT != 0 ]] ; then #It seems sometimes the tests are not dying immediately. Let's give them 10s echo "Suspicious java process found - waiting 10s to see if there are just slow to stop" sleep 10 ZOMBIE_TESTS_COUNT=`jps | grep surefirebooter | wc -l` if [[ $ZOMBIE_TESTS_COUNT != 0 ]] ; then echo "There are $ZOMBIE_TESTS_COUNT zombie tests, they should have been killed by surefire but survived" echo "************ BEGIN zombies jstack extract" ZB_STACK=`jps | grep surefirebooter | cut -d ' ' -f 1 | xargs -n 1 jstack | grep ".test" | grep "\.java"` jps | grep surefirebooter | cut -d ' ' -f 1 | xargs -n 1 jstack echo "************ END zombies jstack extract" JIRA_COMMENT="$JIRA_COMMENT {color:red}-1 core zombie tests{color}. There are ${ZOMBIE_TESTS_COUNT} zombie test(s): ${ZB_STACK}" BAD=1 jps | grep surefirebooter | cut -d ' ' -f 1 | xargs kill -9 else echo "We're ok: there is no zombie test, but some tests took some time to stop" fi else echo "We're ok: there is no zombie test" fi [HBase-0.98] $ /bin/bash -xe /tmp/hudson2233285653493469585.sh ++ jps ++ grep surefirebooter ++ wc -l + ZOMBIE_TESTS_COUNT=0 + [[ 0 != 0 ]] + echo 'We'\''re ok: there is no zombie test' We're ok: there is no zombie test POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 0 Archiving artifacts Sending artifact delta relative to HBase-0.98 #524 Archived 9 artifacts Archive block size is 32768 Received 4 blocks and 56981 bytes Compression is 69.7% Took 1 min 6 sec Recording test results Updating HBASE-12023 Updating HBASE-12021
