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

[13_1_X]changing Era to Run3_2023 for 2023 WFs #41319

Merged
merged 3 commits into from
Apr 18, 2023

Conversation

sunilUIET
Copy link
Contributor

PR description:

This PR is to change era from "Run3" to "Run3_2023" for relval WFs defined for 2023 conditions. Era "Run3_2023" is first introduced in PR #41271 .

PR validation:

Need to be tested with PR #41271

@sunilUIET
Copy link
Contributor Author

sunilUIET commented Apr 11, 2023

@cmsbuild please test with #41271

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41319/35132

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @sunilUIET (sunil bansal) for master.

It involves the following packages:

  • Configuration/PyReleaseValidation (pdmv, upgrade)

@bbilin, @srimanob, @sunilUIET, @kskovpen, @AdrianoDee can you please review it and eventually sign? Thanks.
@makortel, @kpedro88, @Martin-Grunewald, @missirol, @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

@francescobrivio
Copy link
Contributor

Hi @sunilUIET thanks for this!
Just for my understanding: is there a plan to update also all the '--era':'Run3' occurrences in Configuration/PyReleaseValidation/python/relval_steps.py (and all the other release validation scripts)?

@sunilUIET
Copy link
Contributor Author

Hi @sunilUIET thanks for this! Just for my understanding: is there a plan to update also all the '--era':'Run3' occurrences in Configuration/PyReleaseValidation/python/relval_steps.py (and all the other release validation scripts)?

Configuration/PyReleaseValidation/python/relval_steps.py

Hi @francescobrivio , I think we can change it for 2023 WFs only, for the time being, keeping the settings as it is for old WFs. As far as 2023 WFs are concerned, IIUC, it should be enough to change settings in https://github.com/cms-sw/cmssw/blob/master/Configuration/PyReleaseValidation/python/upgradeWorkflowComponents.py#L2364,L2370 and changes should be propagated to all steps.

@sunilUIET
Copy link
Contributor Author

test parameters:

  • relvals_opt= -w upgrade
  • workflows = 12402.0

@sunilUIET
Copy link
Contributor Author

@cmsbuild please test with #41271

@cmsbuild
Copy link
Contributor

-1

Failed Tests: RelVals RelVals-INPUT
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-ba0374/31917/summary.html
COMMIT: ab8f78d
CMSSW: CMSSW_13_1_X_2023-04-11-1100/el8_amd64_gcc11
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/41319/31917/install.sh to create a dev area with all the needed externals and cmssw changes.

RelVals

ValueError: Undefined workflows: 4.53, 4.22, 5.1, 7.3, 8, 9.0, 136.731, 136.7611, 136.8311, 136.88811, 136.793, 136.874, 138.4, 138.5, 139.001, 140.53, 140.56, 12434.0, 23696.0, 23700.0, 25, 1306.0, 23834.999, 158.01, 135.4, 10024.0, 1330, 13234.0, 312.0, 10042.0, 11834.0, 23234.0, 2500.601, 10824.0, 23634.0, 23634.911, 250202.181, 2018.1, 101.0, 1000, 1001, 10224.0, 25202.0, 11634.911, 11634.914, 11634.0, 11634.7, 13434.0
ValueError: Undefined workflows: 12402.0

RelVals-INPUT

@sunilUIET
Copy link
Contributor Author

Hi @sunilUIET

You will need to update this line, https://github.com/cms-sw/cmssw/blob/master/Configuration/PyReleaseValidation/python/upgradeWorkflowComponents.py#L2239 by adding and '2023' not in stepDict[step][k]['--era'] This is to protect the wierd era modification. Then everything should work out-of box without the need for extra workflow.

Thanks @srimanob for the input to solve the issue.

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41319/35159

@cmsbuild
Copy link
Contributor

Pull request #41319 was updated. @bbilin, @srimanob, @sunilUIET, @kskovpen, @AdrianoDee can you please check and sign again.

@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-ba0374/31964/summary.html
COMMIT: 7db6caf
CMSSW: CMSSW_13_1_X_2023-04-12-2300/el8_amd64_gcc11
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/41319/31964/install.sh to create a dev area with all the needed externals and cmssw changes.

  • DAS Queries: The DAS query tests failed, see the summary page for details.

Comparison Summary

Summary:

  • You potentially added 1 lines to the logs
  • Reco comparison results: 2255 differences found in the comparisons
  • DQMHistoTests: Total files compared: 49
  • DQMHistoTests: Total histograms compared: 3619444
  • DQMHistoTests: Total failures: 1173
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3618249
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 48 files compared)
  • Checked 212 log files, 164 edm output root files, 49 DQM output files
  • TriggerResults: no differences found

@sunilUIET
Copy link
Contributor Author

+pdmv

@srimanob
Copy link
Contributor

+Upgrade

@cmsbuild
Copy link
Contributor

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)

@@ -2185,7 +2186,7 @@ def condition(self, fragment, stepList, key, hasHarvest):

class UpgradeWorkflow_DDDDB(UpgradeWorkflow):
def setup_(self, step, stepName, stepDict, k, properties):
if 'Run3' in stepDict[step][k]['--era'] and 'Fast' not in stepDict[step][k]['--era']:
if 'Run3' in stepDict[step][k]['--era'] and '2023' not in stepDict[step][k]['--era'] and 'Fast' not in stepDict[step][k]['--era']:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Just to understand) What is the purpose of this modification?
Should we add 2024, 2025, etc. here in the coming years?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is just a temporary fix to not screw up on modification. The follow up PR should clean this thing out when we have a clear Era, and all necessary Era(s) are in place, i.e. DDD for 2023,4,5 or FastSim for 2023,4,5.

@perrotta
Copy link
Contributor

+1

@swagata87
Copy link
Contributor

do we need a backport of this PR to 13_0_X?

FYI, #41368 this is backport of my PR

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.

6 participants