-
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
[14_0_X] pileup profile for RunIII2024Summer24 MC compaign (backport) #45687
Conversation
A new Pull Request was created by @DickyChant for CMSSW_14_0_X. It involves the following packages:
@antoniovilela, @civanch, @cmsbuild, @davidlange6, @fabiocos, @mandrenguyen, @mdhildreth, @rappoccio can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
cms-bot internal usage |
please test |
-1 Failed Tests: Build BuildI found compilation error when building: SyntaxError: invalid syntax gmake[1]: *** [config/SCRAM/GMake/Makefile.rules:1997: CompilePython] Error 1 gmake[1]: Target 'PostBuild' not remade because of errors. gmake[1]: Leaving directory '/data/cmsbld/jenkins/workspace/ib-run-pr-tests/CMSSW_14_0_X_2024-08-11-2300' gmake: *** [config/SCRAM/GMake/Makefile.rules:1883: src] Error 2 gmake: Target 'all' not remade because of errors. gmake: *** [There are compilation/build errors. Please see the detail log above.] Error 2 + eval scram build outputlog '&&' '(python3' /data/cmsbld/jenkins/workspace/ib-run-pr-tests/cms-bot/buildLogAnalyzer.py --logDir /data/cmsbld/jenkins/workspace/ib-run-pr-tests/CMSSW_14_0_X_2024-08-11-2300/tmp/el8_amd64_gcc12/cache/log/src '||' 'true)' ++ scram build outputlog >> Entering Package Configuration/StandardSequences |
@DickyChant please remove merge marks |
Jesus my bad........ |
Pull request #45687 was updated. @antoniovilela, @civanch, @cmsbuild, @davidlange6, @fabiocos, @mandrenguyen, @mdhildreth, @rappoccio can you please check and sign again. |
please test |
+1 Size: This PR adds an extra 24KB to repository Comparison SummarySummary:
|
+1 |
+1 |
I see, I guess it was related to the fact that the original PR #45474 is going after the original PR of #45686 (i.e. #44686) ... |
I just resolved the conflict... apologize for the mess! |
please test |
+1 Size: This PR adds an extra 24KB to repository The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
You can see more details here: Comparison SummarySummary:
|
is it possible to avoid the nasty merge commit by rebasing? |
Did my exercise in the afternoon, not seems to work (since I cannot find a proper |
cmsrel CMSSW_14_0_X_2024-08-20-1100
cd CMSSW_14_0_X_2024-08-20-1100/src/
cmsenv
git cms-merge-topic 45687
git rebase -i CMSSW_14_0_X
# fix conflicts by hand
git rebase --contine
git cms-init
git push my-cmssw +HEAD:backport_2024_PU seems to work for me: link |
agh you mean improve this one? Sure I'll do it |
pileup profile for RunIII2024Summer24 MC compaign
1482449
to
602c141
Compare
please test |
+1 Size: This PR adds an extra 12KB to repository The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
You can see more details here: Comparison SummarySummary:
|
+1 |
PR description:
Backport of #45474
Introducing pileup profiles for RunIII2024Summer24 MC compaigns
PR validation:
Tested with CMSSW runtests
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:
Since this PR will be used for 2024 MC campaigns, it is intended to be packported to 14_0_X (as described in recent PPD news