Bug #4313: osmo-bts-test left trxcon.log as root ?!? - Core testing infrastructure - Open Source Mobile Communications

Actions

Copy link

Bug #4313

closed

osmo-bts-test left trxcon.log as root ?!?

Added by laforge over 4 years ago. Updated over 4 years ago.

Status:

Resolved

Priority:

Urgent

Assignee:

pespin

Target version:

Start date:

12/06/2019

Due date:

% Done:

100%

Spec Reference:

Description

See https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/726/console

Started by timer
Running as SYSTEM
Building remotely on build2-deb9build-ansible (ttcn3 obs osmo-gsm-tester-build osmocom-gerrit-debian9 osmocom-master-debian9 coverity) in workspace /home/osmocom-build/jenkins/workspace/ttcn3-bts-test
No credentials specified
Wiping out workspace first.
jenkins.util.io.CompositeIOException: Unable to delete '/home/osmocom-build/jenkins/workspace/ttcn3-bts-test'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts.

root@build2-deb9build-ansible:/home/osmocom-build/jenkins/workspace/ttcn3-bts-test# ls -lR .
.:
total 4
drwxr-xr-x 3 osmocom-build osmocom-build 4096 Dec  6 07:00 logs

./logs:
total 4
drwxr-xr-x 3 root root 4096 Dec  5 07:01 trxcon

./logs/trxcon:
total 2648
-rw-r--r-- 1 root root 2701494 Dec  5 07:40 trxcon.log
drwxr-xr-x 2 root root    4096 Dec  5 07:01 unix

./logs/trxcon/unix:

I'm not quite sure how that would happen?

Actions

Copy link

Updated by laforge over 4 years ago

I manually removed the respective files and re-triggered the job. However, it remains to be investigated how this happens and how to prevent it in the future.

Actions

Copy link