Removing JENKINS_PREFIX Check from das-up-to-nevents.py#49636
Removing JENKINS_PREFIX Check from das-up-to-nevents.py#49636cmsbuild merged 1 commit intocms-sw:masterfrom
JENKINS_PREFIX Check from das-up-to-nevents.py#49636Conversation
|
cms-bot internal usage |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-49636/47176 |
|
A new Pull Request was created by @AdrianoDee for master. It involves the following packages:
@AdrianoDee, @DickyChant, @antoniovagnerini, @cmsbuild, @miquork can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
please test |
|
+1 Size: This PR adds an extra 24KB to repository Comparison SummaryThe workflows 2025.0010001, 2025.0000001, 2024.0070001, 2024.0060001, 2024.0050001, 2024.0040001, 2024.0030001, 2024.0020001, 2024.0010001, 2024.0000001, 2023.0020001, 2022.0030001 have different files in step1_dasquery.log than the ones found in the baseline. You may want to check and retrigger the tests if necessary. You can check it in the "files" directory in the results of the comparisons Summary:
Max Memory Comparisons exceeding threshold@cms-sw/core-l2 , I found 12 workflow step(s) with memory usage exceeding the error threshold:
|
|
+pdmv |
|
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. @sextonkennedy, @mandrenguyen, @ftenchini (and backports should be raised in the release meeting by the corresponding L2) |
|
oddly enough I don't see this wf in the dqm bin by bin comparison: |
JENKINS Check from das-up-to-nevents.pyJENKINS_PREFIX Check from das-up-to-nevents.py
|
This is ... strange. Indeed, it's not there, but it has run, and I don't see anything strange in the bot logs ...? |
|
+1 |
PR description:
Triggered by the discussion in #49627. As is
das-up-to-nevents.py, checks if we are running within Jenkins. This was done at the time since, to simplifydas-up-to-neventswhen running PR tests, just to avoid crashes. In #49020 and #49045 the crashes were understood to be coming from accessing the certification web page too many times. Now the bot access the JSONs fromcvmfs.This PR proposes to just remove the
testinglimitation for the bot, allowing PR tests to use certified lumisections.