[
https://issues.apache.org/jira/browse/HBASE-20314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16419680#comment-16419680
]
Mike Drob commented on HBASE-20314:
-----------------------------------
Disk space:
{noformat}
Filesystem Size Used Avail Use% Mounted on
udev 24G 12K 24G 1% /dev
tmpfs 4.8G 840K 4.8G 1% /run
/dev/dm-0 3.6T 312G 3.1T 10% /
none 4.0K 0 4.0K 0% /sys/fs/cgroup
none 5.0M 0 5.0M 0% /run/lock
none 24G 160K 24G 1% /run/shm
none 100M 0 100M 0% /run/user
/dev/sda2 237M 209M 16M 94% /boot
none 3.6T 312G 3.1T 10%
/var/lib/docker/aufs/mnt/bfbf7bc140d62bf886ab61fd0297b74ed99a03cb9ff54a27be9f0853487637ed
{noformat}
ulimits
{noformat}
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 386176
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
{noformat}
Both of those look normal...
In general, this looks related?
https://stackoverflow.com/questions/46670582/docker-maven-failsafe-surefire-starting-fork-fails-with-the-forked-vm-termin
> Pre commit build for master branch fails
> ----------------------------------------
>
> Key: HBASE-20314
> URL: https://issues.apache.org/jira/browse/HBASE-20314
> Project: HBase
> Issue Type: Bug
> Reporter: Duo Zhang
> Priority: Major
> Attachments: HBASE-20314.patch
>
>
> See here
> https://builds.apache.org/job/PreCommit-HBASE-Build/12208/artifact/patchprocess/patch-unit-hbase-client.txt
> All the surefire tests are failed with
> {noformat}
> [ERROR] Please refer to /testptch/hbase/hbase-client/target/surefire-reports
> for the individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /testptch/hbase/hbase-client &&
> /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -enableassertions
> -Dhbase.build.id=2018-03-29T14:24:09Z -Xmx2800m
> -Djava.security.egd=file:/dev/./urandom -Djava.net.preferIPv4Stack=true
> -Djava.awt.headless=true -jar
> /testptch/hbase/hbase-client/target/surefire/surefirebooter6093376455951697188.jar
> /testptch/hbase/hbase-client/target/surefire 2018-03-29T14-24-22_719-jvmRun1
> surefire3061343808153644548tmp surefire_07554325011124878578tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
