You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@impala.apache.org by Jim Apple <jb...@cloudera.com> on 2018/09/08 17:08:05 UTC
expr-benchmark
I can't get exp-benchmark working near HEAD. Has anyone else seen and
solved this? We don't run benchmarks in pre-commit testing, so I'm not
sure if this is just me, perhaps something abut it not being hermetic,
or if this has been broken for a while.
18/09/08 10:00:40 INFO util.JvmPauseMonitor: Starting JVM pause monitor
Wrote minidump to
/tmp/minidumps/expr-benchmark/11ed5026-eff4-4214-639a048a-0389c5c4.dmp
Wrote minidump to
/tmp/minidumps/expr-benchmark/11ed5026-eff4-4214-639a048a-0389c5c4.dmp
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x0000000000e99791, pid=30887, tid=0x00007fb47665f8c0
#
# JRE version: Java(TM) SE Runtime Environment (8.0_131-b11) (build
1.8.0_131-b11)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.131-b11 mixed mode
linux-amd64 compressed oops)
# Problematic frame:
# C [expr-benchmark+0xa99791]
impala::DescriptorTbl::GetSlotDescriptor(int) const+0x1
#
# Failed to write core dump. Core dumps have been disabled. To enable
core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/jbapple/Impala/logs/hs_err_pid30887.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Re: expr-benchmark
Posted by Sailesh Mukil <mu...@gmail.com>.
The benchmarks weren't being actively maintained last I saw (6 months back
or so), and most of them aren't run regularly as well. So a lot of the
dependent code may have changed causing them to break. So, there's no
guarantee that they will work.
On Sat, Sep 8, 2018 at 10:08 AM Jim Apple <jb...@cloudera.com> wrote:
> I can't get exp-benchmark working near HEAD. Has anyone else seen and
> solved this? We don't run benchmarks in pre-commit testing, so I'm not
> sure if this is just me, perhaps something abut it not being hermetic,
> or if this has been broken for a while.
>
> 18/09/08 10:00:40 INFO util.JvmPauseMonitor: Starting JVM pause monitor
> Wrote minidump to
> /tmp/minidumps/expr-benchmark/11ed5026-eff4-4214-639a048a-0389c5c4.dmp
> Wrote minidump to
> /tmp/minidumps/expr-benchmark/11ed5026-eff4-4214-639a048a-0389c5c4.dmp
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x0000000000e99791, pid=30887,
> tid=0x00007fb47665f8c0
> #
> # JRE version: Java(TM) SE Runtime Environment (8.0_131-b11) (build
> 1.8.0_131-b11)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.131-b11 mixed mode
> linux-amd64 compressed oops)
> # Problematic frame:
> # C [expr-benchmark+0xa99791]
> impala::DescriptorTbl::GetSlotDescriptor(int) const+0x1
> #
> # Failed to write core dump. Core dumps have been disabled. To enable
> core dumping, try "ulimit -c unlimited" before starting Java again
> #
> # An error report file with more information is saved as:
> # /home/jbapple/Impala/logs/hs_err_pid30887.log
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.java.com/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
>