After some investigation, it was found that the abort is due to a broken filesystem:
e2fsck 1.46.2 (28-Feb-2021) Warning: skipping journal recovery because doing a read-only filesystem check. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Entry 'stdout' in /var/tmp/test_results/20220107T162910/channel_program/lua_core/tst.memory_limit (2753306) has an incorrect filetype (was 1, should be 2). Fix? no Entry 'stdout' in /var/tmp/test_results/20220107T162910/channel_program/lua_core/tst.memory_limit (2753306) is a link to directory /var/tmp/test_results/20220107T173340/acl/off (2753307). Clear? no Pass 3: Checking directory connectivity Pass 4: Checking reference counts Inode 2753307 ref count is 5, should be 6. Fix? no Pass 5: Checking group summary information Block bitmap differences: -(18451--18516) Fix? no Free blocks count wrong (29962138, counted=29913053). Fix? no Free inodes count wrong (7795602, counted=7775599). Fix? no du-SIGABRT-vda: ********** WARNING: Filesystem still has errors ********** du-SIGABRT-vda: 68718/7864320 files (0.8% non-contiguous), 1495142/31457280 blocks
Daniel Grittner | Junior Software Developer
Celonis SE | Theresienstrasse 6 | 80333 Munich, Germany
F: +4989416159679
d.gri...@celonis.com | www.celonis.com | LinkedIn | Twitter | Xing
AG Munich HRB 225439 | Management: Martin Klenk, Bastian Nominacher, Alexander Rinke
This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.