CostAccountingSpec fails non-deterministically with a SEGFAULT (flaky test)

Description

The test "stop the evaluation of all execution branches when one of them runs out of phlo with a more sophisiticated contract" in CostAccountingSpec fails notoriously with the following error:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f0fda9a4d44, pid=20806, tid=0x00007f0f58b5a700 # # JRE version: OpenJDK Runtime Environment (8.0_212-b03) (build 1.8.0_212-8u212-b03-0ubuntu1.16.04.1-b03) # Java VM: OpenJDK 64-Bit Server VM (25.212-b03 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libpthread.so.0+0x9d44] pthread_mutex_lock+0x4 # # 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/artur/projects/rchain-bloop/hs_err_pid20806.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. # Process finished with exit code 134 (interrupted by signal 6: SIGABRT)

At the very least, it should be made stable (no longer fail with a segfault, pass consistently).
Ideally, we'd find and fix any underlying issues with the tested code. (optional for this ticket).

Environment

None

Status

Assignee

Unassigned

Reporter

Artur Gajowy

Priority

Medium

Affects versions

None

Components

Sprint

Epic Link

None

Labels