[RTADPA BW Tests] Several issues in the PR Jobs [03-Feb]

---

---

---

spruce_'nominal' GitANNSvc error

spruce_'nominal' is failing in the line-and-stream-rates.sh jobs. i.e. Obtaining rates and bandwidth for wg-stream configuration with a GitAnnSvc error. Odd because we seemingly propagate the tck.json correctly in from the 'main' Moore job where we generate the spruced sample. What changed to cause this problem needs more investigation.

EventSelector     SUCCESS Reading Event record 1. Record number within stream 1: 1
EventPersistenc...   INFO Added successfully Conversion service:RootCnvSvc
EventPersistenc...   INFO Added successfully Conversion service:LHCb::RawDataCnvSvc
Hlt2DecReportsD...  ERROR GitANNSvc::fetch : unable to obtain json for key 0b42613e from repositories [ ( '/home/lhcbpr/jenkins/perf/workspace/nightly-builds/tests/output/lhcb-metainfo/.git' , 'master' ) , ( '/cvmfs/lhcb-condb.cern.ch/git-conddb/file-content-metadata.git' , 'master' ) ]
Hlt2DecReportsD...  ERROR Maximum number of errors ( 'ErrorMax':1) reached.
EventLoopMgr      WARNING Execution of algorithm Hlt2DecReportsDecoder failed
HltANNSvc         WARNING key 0x9a2ff9e8 has an explicitly configured overrule -- using that...
EventLoopMgr        ERROR Error processing event loop.
EventLoopMgr        ERROR Terminating event processing loop due to errors
EventLoopMgr        ERROR Terminating event processing loop due to errors

---

---

---

ToDo:

• spruce_latest and hlt2_and_spruce muon_geometry errors. see: !383 (merged)
• spruce_latest and hlt2_and_spruce wrong TisTos info. see: see: !383 (merged) + lhcb-core/LHCbPR2HD!276 (merged) + lhcb/Moore!2943 (merged)
• spruce_latest input-data value. see: !383 (merged)
• spruce_'nominal' GitANNSvc error. see discussion
• hlt2_and_spruce upload {process}__index too. see: lhcb-core/LHCbPR2HD!275 (merged)
• All tests $$comparison$$ page. see: !383 (merged)
  • hlt2_and_spruce replace $$comparison$$ in {process}__index.html too. see: lhcb-core/LHCbPR2HD!275 (merged)
• hlt2 uploaded metadata.yaml incorrect. see: !383 (merged)