Fix DQM Certification JSON Parsing From Web in das-up-to-nevents.py

[AdrianoDee]

PR description:

Apparenlty the names of the certification jsons have changed in https://cms-service-dqmdc.web.cern.ch/CAF/certification/Collisions24/ and this is causing das-up-to-nevents.py to fail.

PR validation:

das-up-to-nevents.py -d /JetMET0/Run2024D-v1/RAW -e 10000 runs with web fallback.

[AdrianoDee]

type bug-fix

[cmsbuild]

cms-bot internal usage

[AdrianoDee]

please test

[AdrianoDee]

urgent

To fix PR tests

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-46559/42440

[cmsbuild]

A new Pull Request was created by @AdrianoDee for master.

It involves the following packages:

• Configuration/PyReleaseValidation (pdmv, upgrade)

@AdrianoDee, @Moanwar, @kskovpen, @miquork, @srimanob, @subirsarkar, @sunilUIET can you please review it and eventually sign? Thanks.
@Martin-Grunewald, @fabiocos, @makortel, @missirol, @slomeo this is something you requested to watch as well.
@antoniovilela, @mandrenguyen, @rappoccio, @sextonkennedy you are the release manager for this.

cms-bot commands are listed here

[smuzaffar]

@AdrianoDee , this can happen in future again ... right? How we can avoid this ?

[AdrianoDee]

@AdrianoDee , this can happen in future again ... right? How we can avoid this ?

In principle it should be safe now. What changed was not really the name of the json the wfs target (that is still Cert_{Collisions|Cosmics}YEAR_Run1_RunN_{Golden|Muon}.json). It was the naming of those to be discarded from the list. As is they will be discarded earlier in the chain. I don't expect the standard json to change name without being properly announced.

On a side note, I don't understand why the bot tests do not see /eos/user/c/cmsdqm/www/CAF/certification/ (that would avoid to use the website fallback).

[smuzaffar]

@AdrianoDee , eos is not mounted on build nodes that is why /eos/user/c/cmsdqm/www/CAF/certification/ is not accessible

[AdrianoDee]

@AdrianoDee , eos is not mounted on build nodes that is why /eos/user/c/cmsdqm/www/CAF/certification/ is not accessible

Understood, thanks. Didn't know it

[cmsbuild]

+1

Size: This PR adds an extra 16KB to repository
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-109497/42486/summary.html
COMMIT: 3478e78
CMSSW: CMSSW_14_2_X_2024-10-30-1100/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/46559/42486/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

• You potentially removed 1 lines from the logs
• Reco comparison results: 6 differences found in the comparisons
• DQMHistoTests: Total files compared: 46
• DQMHistoTests: Total histograms compared: 3569372
• DQMHistoTests: Total failures: 506
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3568846
• DQMHistoTests: Total skipped: 20
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 45 files compared)
• Checked 201 log files, 171 edm output root files, 46 DQM output files
• TriggerResults: no differences found

[AdrianoDee]

+pdmv

[AdrianoDee]

@cms-sw/upgrade-l2 let me know if this is fine for you: it would fix all the PR failures.

[Moanwar]

+Upgrade
Thanks! @AdrianoDee

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @antoniovilela, @sextonkennedy, @mandrenguyen, @rappoccio (and backports should be raised in the release meeting by the corresponding L2)

[mandrenguyen]

+1