My guess would be something alog these lines
```
if (nActualStrips == 0) {
cout << "No valid strips found, insufficient statistics." << endl;
} else {
```
but perhaps the @cms-sw/l1...
+1
**Size**: This PR adds an extra 948KB to repository
**Summary**: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-15790b/42394/summary.html
**COMMIT**: 4e595751f837b61e4...
+1
**Size**: This PR adds an extra 948KB to repository
**Summary**: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-44c4cd/42393/summary.html
**COMMIT**: 9c7d261e88c7100fa...
The workspace for el9_amd64_gcc12 has been deleted
You can see the log here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/cleanup-auto-build/CMSSW_14_1_4_patch1-el9_amd64_gcc12/3084
The workspace for slc7_amd64_gcc12 has been deleted
You can see the log here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/cleanup-auto-build/CMSSW_14_1_4_patch1-slc7_amd64_gcc12/3085
The workspace for el9_aarch64_gcc12 has been deleted
You can see the log here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/cleanup-auto-build/CMSSW_14_1_4_patch1-el9_aarch64_gcc12/3083
The workspace for el8_amd64_gcc12 has been deleted
You can see the log here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/cleanup-auto-build/CMSSW_14_1_4_patch1-el8_amd64_gcc12/3082
The workspace for el8_aarch64_gcc12 has been deleted
You can see the log here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/cleanup-auto-build/CMSSW_14_1_4_patch1-el8_aarch64_gcc12/3081
The tests have finished for slc7_amd64_gcc12
You can see the log here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/auto-build-release/CMSSW_14_1_4_patch2-slc7_amd64_gcc12/4657
Tests results...
The tests have finished for el8_amd64_gcc12
You can see the log here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/auto-build-release/CMSSW_14_1_4_patch2-el8_amd64_gcc12/4655
Tests results:
...
The tests have finished for el9_amd64_gcc12
You can see the log here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/auto-build-release/CMSSW_14_1_4_patch2-el9_amd64_gcc12/4656
Tests results:
...
In 29634.0 (TTbar 2026D110) step 3 (reco) the number of allocations decreases from 250 million to 245 million, i.e. a reduction of 4.9 million or 2.0 %.
The ~8 MB increase in maxmemory is likely related to #46359 and the substantial number of packages being checked out.
Looking at the logs directly, e.g. 141.046 (EGamma 2023D) step 3 (reco) the ...