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

Request to build CMSSW_13_2_1 #42569

Closed
5 tasks done
missirol opened this issue Aug 15, 2023 · 24 comments
Closed
5 tasks done

Request to build CMSSW_13_2_1 #42569

missirol opened this issue Aug 15, 2023 · 24 comments

Comments

@missirol
Copy link
Contributor

missirol commented Aug 15, 2023

(Since there is likely no ORP meeting, I'm asking this via a GitHub issue, which is maybe better than email to involve all interested parties.)

HLT would like to have a new release of CMSSW_13_2_X. That would be CMSSW_13_2_1, afaik.

  • #42489 (merged) is needed to build the 2023 HIon menu in ConfDB.
  • TSG is also requesting to include #42559 (which depends on cmsdist#8646) in this next 13_2_X release, for GPU-related developments for HLT.
  • (A few other PRs relevant to HLT and/or HIon have also been merged already in CMSSW_13_2_X since CMSSW_13_2_0.)

Other groups can list here their needs for CMSSW_13_2_1.

Preferred timeline: by the end of this week.

FYI: @cms-sw/hlt-l2 @fwyzard @silviodonato @mmusich


List of PRs targeting CMSSW_13_2_1:

Type of non-standard builds:

@cmsbuild
Copy link
Contributor

A new Issue was created by @missirol Marino Missiroli.

@Dr15Jones, @perrotta, @dpiparo, @rappoccio, @makortel, @smuzaffar can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

@missirol
Copy link
Contributor Author

assign orp

@cmsbuild
Copy link
Contributor

New categories assigned: orp

@perrotta,@dpiparo,@rappoccio you have been requested to review this Pull request/Issue and eventually sign? Thanks

@cmsbuild
Copy link
Contributor

This issue is fully signed and ready to be closed.

@missirol
Copy link
Contributor Author

The "fully signed" part was not intended. :)

@fwyzard
Copy link
Contributor

fwyzard commented Aug 15, 2023

If possible, let me add two requests:

@mmusich
Copy link
Contributor

mmusich commented Aug 15, 2023

Might be convenient to wait also for #42545

@missirol
Copy link
Contributor Author

The PRs mentioned so far for 13_2_1 are merged (I left a list at the bottom of the description). I don't see other urgent PRs in the 13_2_X queue, so from my point of view things are ready.

@Martin-Grunewald
Copy link
Contributor

Apparently one more PR needed before building (to fix an issue similar to #42489 )

@perrotta
Copy link
Contributor

Apparently one more PR needed before building (to fix an issue similar to #42489 )

And the PR number is? When it is expected?

@Martin-Grunewald
Copy link
Contributor

Sorry, not available yet (mentioned in TSG meeting today).

@mmusich
Copy link
Contributor

mmusich commented Aug 16, 2023

if we are to wait, I would be glad if we could throw in #42583 as well.

@missirol
Copy link
Contributor Author

I added #42583 and "backport of #42584" to the list. Hopefully these can be ready by tomorrow.

@mmusich
Copy link
Contributor

mmusich commented Aug 16, 2023

"backport of #42584" is #42585

@perrotta
Copy link
Contributor

Type of non-standard builds:

@smuzaffar is there a way to request the build of this architecture on top of all standard ones (i.e. without having to list them one by one [1])?

[1] https://cms-sw.github.io/build-release.html

@antoniovilela
Copy link
Contributor

Started 13_2_1 build (#42596). Will wait for this to finish to build the SKYLAKEAVX.

@missirol
Copy link
Contributor Author

Thanks, @cms-sw/orp-l2 @antoniovilela !

@fwyzard
Copy link
Contributor

fwyzard commented Aug 17, 2023

Thank you!

@perrotta
Copy link
Contributor

The CMSSW_13_2_1 release is ready with all the requested PRs: https://github.com/cms-sw/cmssw/releases/tag/CMSSW_13_2_1
As soon as also the SKYLAKEAVX512 build will become available this issue can get closed

@perrotta
Copy link
Contributor

@perrotta
Copy link
Contributor

+orp

@missirol
Copy link
Contributor Author

please close

(For the record, the bot got confused in #42569 (comment), and this should maybe be improved.)

@perrotta
Copy link
Contributor

(For the record, the bot got confused in #42569 (comment), and this should maybe be improved.)

Well, in any case it was an action required for orp, then the assignment was not even too wrong :-)

@mmusich
Copy link
Contributor

mmusich commented Aug 21, 2023

in any case it was an action required for orp, then the assignment was not even too wrong :-)

I think the problem here is that (afaiu) the bot couples orp-pending with the fully-signed labels which is generally suitable in ordinary PRs (since no PR is purely under ORP), but not OK here, since there was no action pending from other groups.

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

No branches or pull requests

7 participants