Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make _relval GTs symbolic and resnapshot Run3 data GTs #40692

Merged
merged 1 commit into from
Feb 7, 2023

Conversation

tvami
Copy link
Contributor

@tvami tvami commented Feb 4, 2023

PR description:

Discussed in https://cms-talk.web.cern.ch/t/reviewing-auto-relval-content-and-making-it-symbolic-gt/19584
We make the _relval GTs symbolic since they change less often and this way we can avoid mismatches between the GT and the GTs meant to be used with a fixed L1T menu.

We also propose to move away from using the offline (rereco) GT for data validations in the relvals, they should use the prompt GT instead (which in Run-3 is certainly almost already physics quality).

To be consistent with the relval GT, the frozen GTs were resnapshoted as well. The diff in GTs is just in the visible IOVs:

There is a lot of things using auto:run3_data
https://github.com/cms-sw/cmssw/search?p=2&q=auto%3Arun3_data
which we should probably revise, but that is beyond this PR.

PR validation:

test parameters:
  - workflows = 139.004

runs fine.

If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:

Not a backport. Given the GT names and that the current data taking release is 12_6_X, it would make sense to backport to 12_6_X

@tvami
Copy link
Contributor Author

tvami commented Feb 4, 2023

test parameters:

  • workflows = 139.004

@tvami
Copy link
Contributor Author

tvami commented Feb 4, 2023

@sunilUIET are the relvals at pre-releases taking a wf number from CMSSW, or does that run through some other system?

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 4, 2023

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-40692/34052

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 4, 2023

A new Pull Request was created by @tvami (Tamas Vami) for master.

It involves the following packages:

  • Configuration/AlCa (alca)
  • Configuration/HLT (hlt)
  • Configuration/PyReleaseValidation (pdmv, upgrade)

@malbouis, @yuanchao, @AdrianoDee, @bbilin, @Martin-Grunewald, @cmsbuild, @missirol, @srimanob, @saumyaphor4252, @kskovpen, @sunilUIET, @tvami, @ChrisMisan, @francescobrivio can you please review it and eventually sign? Thanks.
@makortel, @kpedro88, @Martin-Grunewald, @missirol, @silviodonato, @tocheng, @mmusich, @fabiocos, @slomeo this is something you requested to watch as well.
@perrotta, @dpiparo, @rappoccio you are the release manager for this.

cms-bot commands are listed here

@tvami
Copy link
Contributor Author

tvami commented Feb 4, 2023

@cmsbuild , please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 4, 2023

-1

Failed Tests: RelVals AddOn
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-124270/30395/summary.html
COMMIT: 6caf451
CMSSW: CMSSW_13_0_X_2023-02-03-1100/el8_amd64_gcc11
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/40692/30395/install.sh to create a dev area with all the needed externals and cmssw changes.

RelVals

----- Begin Fatal Exception 04-Feb-2023 03:41:20 CET-----------------------
An exception of category 'ConditionDatabase' occurred while
   [0] Constructing the EventProcessor
   [1] Constructing ESSource: class=PoolDBESSource label='GlobalTag'
Exception Message:
Tag "L1Menu_Collisions2015_25nsStage1_v5L" has not been found in the database. from IOVProxy::load 
----- End Fatal Exception -------------------------------------------------
----- Begin Fatal Exception 04-Feb-2023 03:41:45 CET-----------------------
An exception of category 'ConditionDatabase' occurred while
   [0] Constructing the EventProcessor
   [1] Constructing ESSource: class=PoolDBESSource label='GlobalTag'
Exception Message:
Tag "L1Menu_Collisions2015_25nsStage1_v5L" has not been found in the database. from IOVProxy::load 
----- End Fatal Exception -------------------------------------------------
----- Begin Fatal Exception 04-Feb-2023 03:41:45 CET-----------------------
An exception of category 'ConditionDatabase' occurred while
   [0] Constructing the EventProcessor
   [1] Constructing ESSource: class=PoolDBESSource label='GlobalTag'
Exception Message:
Tag "L1Menu_Collisions2015_25nsStage1_v5L" has not been found in the database. from IOVProxy::load 
----- End Fatal Exception -------------------------------------------------
Expand to see more relval errors ...

AddOn Tests

----- Begin Fatal Exception 04-Feb-2023 03:41:58 CET-----------------------
An exception of category 'ConfigFileReadError' occurred while
   [0] Processing the python configuration file named /cvmfs/cms-ib.cern.ch/sw/x86_64/nweek-02770/el8_amd64_gcc11/cms/cmssw/CMSSW_13_0_X_2023-02-03-1100/src/HLTrigger/Configuration/test/OnLine_HLT_GRun.py
Exception Message:
 unknown python problem occurred.
AttributeError: 'tuple' object has no attribute 'split'

At:
  /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/40692/30395/CMSSW_13_0_X_2023-02-03-1100/src/Configuration/AlCa/python/GlobalTag.py(99): GlobalTag
  /cvmfs/cms-ib.cern.ch/sw/x86_64/nweek-02770/el8_amd64_gcc11/cms/cmssw/CMSSW_13_0_X_2023-02-03-1100/src/HLTrigger/Configuration/test/OnLine_HLT_GRun.py(87664): <module>

----- End Fatal Exception -------------------------------------------------
----- Begin Fatal Exception 04-Feb-2023 03:41:55 CET-----------------------
An exception of category 'ConfigFileReadError' occurred while
   [0] Processing the python configuration file named /cvmfs/cms-ib.cern.ch/sw/x86_64/nweek-02770/el8_amd64_gcc11/cms/cmssw/CMSSW_13_0_X_2023-02-03-1100/src/HLTrigger/Configuration/test/OnLine_HLT_HIon.py
Exception Message:
 unknown python problem occurred.
AttributeError: 'tuple' object has no attribute 'split'

At:
  /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/40692/30395/CMSSW_13_0_X_2023-02-03-1100/src/Configuration/AlCa/python/GlobalTag.py(99): GlobalTag
  /cvmfs/cms-ib.cern.ch/sw/x86_64/nweek-02770/el8_amd64_gcc11/cms/cmssw/CMSSW_13_0_X_2023-02-03-1100/src/HLTrigger/Configuration/test/OnLine_HLT_HIon.py(26884): <module>

----- End Fatal Exception -------------------------------------------------
----- Begin Fatal Exception 04-Feb-2023 03:42:04 CET-----------------------
An exception of category 'ConfigFileReadError' occurred while
   [0] Processing the python configuration file named /cvmfs/cms-ib.cern.ch/sw/x86_64/nweek-02770/el8_amd64_gcc11/cms/cmssw/CMSSW_13_0_X_2023-02-03-1100/src/HLTrigger/Configuration/test/OnLine_HLT_PIon.py
Exception Message:
 unknown python problem occurred.
AttributeError: 'tuple' object has no attribute 'split'

At:
  /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/40692/30395/CMSSW_13_0_X_2023-02-03-1100/src/Configuration/AlCa/python/GlobalTag.py(99): GlobalTag
  /cvmfs/cms-ib.cern.ch/sw/x86_64/nweek-02770/el8_amd64_gcc11/cms/cmssw/CMSSW_13_0_X_2023-02-03-1100/src/HLTrigger/Configuration/test/OnLine_HLT_PIon.py(5283): <module>

----- End Fatal Exception -------------------------------------------------
Expand to see more addon errors ...

@sunilUIET
Copy link
Contributor

Hi @tvami , as far as I understand so far, WF numbers are coming from CMSSW as defined in relval_standard/upgrade.py. If there are some hidden steps, I let @kskovpen comment.

@missirol
Copy link
Contributor

missirol commented Feb 4, 2023

@tvami

  • I guess L1Menu_Collisions2015_25nsStage1_v5L is just a typo (it's L1Menu_Collisions2015_25nsStage1_v5).

  • In order to make the addOnTests work, please update autoCondHLT.py as follows:

    git checkout CMSSW_13_0_0_pre3 "${CMSSW_BASE}"/src/Configuration/HLT/python/autoCondHLT.py
    sed -i "s|_relval'|'       |g" "${CMSSW_BASE}"/src/Configuration/HLT/python/autoCondHLT.py
    sed -i "s|run1_hlt'       |run1_hlt_relval'|g" "${CMSSW_BASE}"/src/Configuration/HLT/python/autoCondHLT.py
    sed -i "s|run2_hlt'       |run2_hlt_relval'|g" "${CMSSW_BASE}"/src/Configuration/HLT/python/autoCondHLT.py

Additional questions:

  • Why isn't run2_hlt_relval made 'symbolic' as well?

  • Is run1_hlt_relval only used in autoCondHLT.py#L44? If so, and if it is okay with AlCa, you could remove run1_hlt_relval from autoCond.py, and change run1_hlt_relval to run2_hlt_relval in autoCondHLT.py (or to run2_hlt if that is added to make run2_hlt_relval 'symbolic').

@tvami
Copy link
Contributor Author

tvami commented Feb 6, 2023

hi @missirol , thanks for your comments,

sed -i "s|_relval'|' |g" "${CMSSW_BASE}"/src/Configuration/HLT/python/autoCondHLT.py

is this really intended? There is no run3_hlt_relval like this

Why isn't run2_hlt_relval made 'symbolic' as well?

Because there is no run2_hlt key. I can make it tho.

If so, and if it is okay with AlCa, you could remove run1_hlt_relval from autoCond.py

ok I'll do that too

@missirol
Copy link
Contributor

missirol commented Feb 6, 2023

is this really intended? There is no run3_hlt_relval like this

Yes, that is the idea. What autoCondHLT.py effectively does is to customise the GT "X" with a fixed L1T menu decided by TSG, so "X" can just be run3_hlt as long as the difference between run3_hlt and run3_hlt_relval is only the L1T-menu tag.

The other questions hint at the fact that, if some updates are done upstream (e.g. adding run2_hlt), we could remove all mentions of _relval in autoCondHLT.py. (not saying it's a big gain, it just seems clearer to me that way)

@missirol
Copy link
Contributor

missirol commented Feb 7, 2023

+hlt

@kskovpen
Copy link
Contributor

kskovpen commented Feb 7, 2023

+pdmv

@AdrianoDee
Copy link
Contributor

+1

@francescobrivio
Copy link
Contributor

+alca

  • after private discussion with @cms-sw/alca-l2 and given the urgency (we would like to have this in pre4) we decided that the cleanup of the unwanted symbolic GTs can be done later (see Clean unwanted relval symbolic GTs cms-AlCaDB/AlCaTools#85 opened as reminder). Also, given the fact that these symbolic GTs should be explicitly called somewhere (and they aren't) they remain totally harmless.

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 7, 2023

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. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2)

@perrotta
Copy link
Contributor

perrotta commented Feb 7, 2023

"auto:run2_data_relval" is still needed by

  • Configuration/PyReleaseValidation/python/relval_steps.py
  • CalibTracker/SiPixelQuality/test/step3_SiPixelCalZeroBias_RAW2DIGI_RECO_ALCA.py

@tvami
Copy link
Contributor Author

tvami commented Feb 7, 2023

@perrotta that's fine, we are still providing auto:run2_data_relval, just in a different way. The wf 139.004 is also usig a _relval GT, and as you can see it runs just fine.

@perrotta
Copy link
Contributor

perrotta commented Feb 7, 2023

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants