Project

General

Profile

Bug #3800

Core file breaks jenkins ttcn3 builds

Added by daniel 8 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
02/13/2019
Due date:
% Done:

0%


Description

ttcn3 jenkins jobs fail if the tested component crashes with a core dump.

The issue is that docker runs (for example) osmo-msc as root and if it crashes the core dump generated is also owned by root - but without read permissions for others. Then the jenkins task that collects the artifacts runs as user and fails to read the core file. The log file is also owned by root, but since it is readable by all it can be archived.

https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-msc-test/438/consoleFull

The workspace of osmo-msc-test shows the core file and also shows that it can't be read by jenkins.

One possibility would be to run osmo-msc inside docker as user instead of root, but then you need to ensure that uid inside and outside of docker match. Fixuid seems to do exactly that: https://github.com/boxboat/fixuid

We could just sudo chown -R $USER $VOL_BASE_DIR in jenkins.sh or in the jenkins job after running jenkins.sh if we don't want to have it in the script.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)