-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Developments for DQM Core must be tested also on Online DQM clients before deploying/merging #41713
Comments
A new Issue was created by @sroychow Suvankar Roy Chowdhury. @Dr15Jones, @perrotta, @dpiparo, @rappoccio, @makortel, @smuzaffar can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
assign dqm |
New categories assigned: dqm @tjavaid,@micsucmed,@nothingface0,@rvenditti,@emanueleusai,@syuvivida,@pmandrik you have been requested to review this Pull request/Issue and eventually sign? Thanks |
(I'd like to understand a bit better the testing suggestion)
The clients defined in |
I guess a DQM bin-by-bin comparison of the online client output might have caught the issue. The clients don't fail but (some of) the histograms are not there. |
+1 |
This issue is fully signed and ready to be closed. |
I natively would have thought that DQM would sign once a solution for the issue is proposed. |
In the recent collision runs, several MEs were not displayed on Online GUI( see link). Upon iterating with Central DQM experts, it was understood that the problem is caused by #41400 -
With the above motivation, the proposal is the following:-
Whenever a change to
DQMStore
or any DQM Core is made, the Online clients should also be tested on top of the proposed changes before the relevant PRs are merged.The text was updated successfully, but these errors were encountered: