Chris Jones
Chris Jones
I ran the test TestCTPPSDirectProtonSimulation 3 times in my local checkout and it ran just fine. I'll run the tests again to double check.
please test
please test
So running my tests locally (based on CMSSW_12_5_0_pre4) everything is fine. Wonder if it is an interaction with a more recently merged pull request.
So I was able to reproduce the problem (though subsequent run returned a different value). However, when I dumped the content of the file it was the value stated ```...
@makortel I'm betting the failure is the Wrapper change. In your test, you check out the base, but that does NOT include this pull request. So the test is vulnerable...
Here is some further items. When I run the unit test via scram, I see the contents of the file are ``` root [1] Events->Print() ****************************************************************************** *Tree :Events : *...
If I take the file I hand ran and use if for the step2 part of the unit test, the job runs fine.
The reason you see nearly no benefit in using more threads is the way ROOT uses threads. One and only one thread is allowed to call methods associated with one...
Looking at the job log in the directory given, the job is using 1 thread but is only 39% CPU efficient (CPU time is 21365.2 while the wallclock time is...