Project

General

Profile

Bug #1492

Cpp unit test failure in trunk

Added by Dobbs, Adam about 7 years ago. Updated about 7 years ago.

Status:
Open
Priority:
Normal
Category:
Testing
Target version:
Start date:
23 June 2014
Due date:
% Done:

0%

Estimated time:
Workflow:
New Issue

Description

This has been reported as an aside in another issue but seems to have gotten passed over. Running the cpp unit tests in the trunk on the Imperial SL cluster produces the following error:

[----------] 1 test from PIDVarBTestSetUp
[ RUN      ] PIDVarBTestSetUp.TestSetUpAndTearDown
tests/cpp_unit/Recon/Global/PIDVarBTest.cc:45: Failure
Value of: 0                                           
Expected: gSystem->Unlink(testdir.c_str())            
Which is: -1                                          
[  FAILED  ] PIDVarBTestSetUp.TestSetUpAndTearDown (30 ms)
[----------] 1 test from PIDVarBTestSetUp (30 ms total)   

Suspect due to a distributed filesystem issue. Be great if we could get this fixed before the next release.


Related issues

Related to MAUS - Feature #1497: Require to set production threshold per volumeClosedRogers, Chris25 June 2014

Actions
Related to MAUS - Bug #1548: PIDVarATestSetUp fails in trunkOpen01 September 2014

Actions
#1

Updated by Rajaram, Durga about 7 years ago

It'd be helpful to know if the ROOT unlink failed because of permissions or because the directory wasn't empty.
Can you check if ${MAUS_ROOT_DIR}/files/PID/test_test/ exists, whether it's empty, and what the directory permissions are?

#2

Updated by Dobbs, Adam about 7 years ago

Sure:

[adobbs@heppc158 devel]$ l files/PID/
total 112K
drwxr-sr-x. 2 adobbs muons0 4.0K Jun 10 13:52 test_200MeV_pi_plus_2014_06_10T13_52_43_075894/
drwxr-sr-x. 2 adobbs muons0 4.0K Jun 10 13:52 test_200MeV_pi_plus_2014_06_10T13_52_43_253431/
drwxr-sr-x. 2 adobbs muons0 4.0K Jun 10 13:52 test_200MeV_pi_plus_2014_06_10T13_52_43_306630/
drwxr-sr-x. 2 adobbs muons0 4.0K Jun 10 17:22 test_200MeV_pi_plus_2014_06_10T17_22_31_574003/
drwxr-sr-x. 2 adobbs muons0 4.0K Jun 10 17:22 test_200MeV_pi_plus_2014_06_10T17_22_31_706561/
drwxr-sr-x. 2 adobbs muons0 4.0K Jun 10 17:22 test_200MeV_pi_plus_2014_06_10T17_22_31_776725/
drwxr-sr-x. 2 adobbs muons0 4.0K Jun 10 17:37 test_200MeV_pi_plus_2014_06_10T17_37_41_533749/
drwxr-sr-x. 2 adobbs muons0 4.0K Jun 10 17:37 test_200MeV_pi_plus_2014_06_10T17_37_41_666902/
drwxr-sr-x. 2 adobbs muons0 4.0K Jun 10 17:37 test_200MeV_pi_plus_2014_06_10T17_37_41_732559/
drwxr-sr-x. 2 adobbs muons0 4.0K Jun 23 14:53 test_200MeV_pi_plus_2014_06_23T14_53_58_995336/
drwxr-sr-x. 2 adobbs muons0 4.0K Jun 23 14:53 test_200MeV_pi_plus_2014_06_23T14_53_59_138206/
drwxr-sr-x. 2 adobbs muons0 4.0K Jun 23 14:53 test_200MeV_pi_plus_2014_06_23T14_53_59_206073/
drwxr-sr-x. 2 adobbs muons0 4.0K Jun 23 14:53 test_200MeV_pi_plus_2014_06_23T14_53_59_294331/
drwxr-sr-x. 2 adobbs muons0 4.0K Jun 23 15:09 test_test/
[adobbs@heppc158 devel]$ l files/PID/test_test/
total 0
[adobbs@heppc158 devel]$

#3

Updated by Rajaram, Durga about 7 years ago

I can't reproduce this error on SL. The only way I could get the unlink to fail was to have the directory permission set to "-x".
I've now forced a system removal of the directory pushed to the trunk r754 -- let me know if that works or still fails

#4

Updated by Rogers, Chris about 7 years ago

John Nugent just saw the same error #1497 note 24

#5

Updated by Rajaram, Durga about 7 years ago

Pushed fix to trunk r761

Also available in: Atom PDF