-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
PyReleaseValidation: move DD4hep test workflow into upgrade special wf section #30003
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-30003/15681
|
A new Pull Request was created by @fabiocos (Fabio Cossutti) for master. It involves the following packages: Configuration/PyReleaseValidation @pgunnell, @civanch, @Dr15Jones, @chayanit, @cvuosalo, @wajidalikhan, @ianna, @mdhildreth, @cmsbuild, @makortel, @kpedro88 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@bsunanda this might be of interest for you |
please test |
The tests are being triggered in jenkins. |
Configuration/PyReleaseValidation/python/upgradeWorkflowComponents.py
Outdated
Show resolved
Hide resolved
… a minimal reference
The code-checks are being triggered in jenkins. |
+1 |
Comparison job queued. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
failures are clearly unrelated to this PR (which has no effect in this test, it requires |
+1 |
+upgrade |
@chayanit any comment? |
+1 |
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. @silviodonato, @dpiparo (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR is a follow-up of the discussion in #29975 about the possible workflow to test DD4hep in a standard environment. As now a 2021 full geometry is available, a list of possible workflows fully based on DD4hep can be easily added as suggested by @kpedro88. The workflows themselves are failing, and for this reason they are not made available to the IB or short matrix. But they can be used for routine checks.
As offset ".911" has been chosen, it does not overlaps with any other use to my knowledge.
PR validation:
The list of workflows is just enlarged by the desired addition.