add GPU memory and usage to the phase2 HLT timing check#50479
add GPU memory and usage to the phase2 HLT timing check#50479cmsbuild merged 2 commits intocms-sw:masterfrom
Conversation
|
test parameters:
|
|
cms-bot internal usage |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-50479/48627
|
|
@cmsbuild, please test |
|
+1 Size: This PR adds an extra 24KB to repository HLT P2 Timing: chart Comparison SummarySummary:
|
|
Milestone for this pull request has been moved to CMSSW_17_0_X. Please open a backport if it should also go in to CMSSW_16_1_X. |
8db7080 to
1fcdb57
Compare
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-50479/49068
|
|
Pull request #50479 was updated. |
|
+1 Size: This PR adds an extra 24KB to repository HLT P2 Timing: chart Comparison SummarySummary:
|
|
A new Pull Request was created by @mmusich for master. It involves the following packages:
@Martin-Grunewald, @mmusich can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
+hlt
|
|
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) |
|
+1 |
|
where do the details of the memory usage go? is it just the timing log like |
they go into csv files which are not percolated yet, for the moment you get the summary in the log. |
|
Hi @smuzaffar I am afraid this PR broke the Phase2 HLT timing test in the 17.0.X IBs, see e.g.: On the other hand I am a little puzzled, because the log files look fine to me: Also if I am not missing anything the jenkins log claim SUCCESS: Do you have any hints to what might be wrong? |
|
@mmusich , I see the following message in log file same messages are there for PR tests too the way we run the test for PR is |
@smuzaffar , but then how e.g. are tests failing here: #50679 (comment) ? |
|
there there are failing because after running In recent failure I see and I guess due to these failures the output json files were not created while when PR tests run for this the above error did not happen and test mighthave created the needed json files |
PR description:
Title says it all.
PR validation:
To be tested by the bot.
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:
N/A