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
HLT validation tests #34387
Comments
A new Issue was created by @smuzaffar Malik Shahzad Muzaffar. @Dr15Jones, @dpiparo, @silviodonato, @smuzaffar, @makortel, @qliphy can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
assign hlt |
New categories assigned: hlt @fwyzard,@Martin-Grunewald you have been requested to review this Pull request/Issue and eventually sign? Thanks |
For what release cycles do we expect to run step2 / step3 MC production in the future ? |
What happened, the link to the "HLT Validation Tests" has disappeared from the IB pages: |
That is the (very) old version of the IB pages. The HLT tests are shown in the current IB pages https://cmssdt.cern.ch/SDT/html/cmssdt-ib under the name "HLT" (and it is currently showing failure that is different from #34231 (comment)) @smuzaffar Should we think of removing the old IB pages to avoid confusion? |
yes it is time to get rid of old page (which is not maintained any more). I will announce it to HN and set a apache redirection to go to the new Ib pages |
Partial fix for 80X: #34484 |
@Martin-Grunewald , HLT tests run for all release cycles. Can we stop runing these tests for old release cycles e.g. 5.3.X up to 10.X? |
Hmm, why? Any specific reason? |
Takes a lot of build resources (e.g. over 3 hours per IB on a 24 core machine). Although we do not build older release cycles every day but on Sunday (when we force build all IBs) it slows down the builds. |
Well, I would be in favor of closing more currently active CMSSW releases to lighten the load, but if it helps then ok, stop the tests for old releases but keep them for 11 and up. |
Coming back to this, last week during Core SW meeting we discussed this again and would like to stop HLT tests for CMSSW 5.X till 10.X release cycles. This will still leave 10 releases cycles (11.0.X up to 13.0.X) for which we will run HLT tests. By the way, in old release cycles this test was taking 2-3 hours on 24 code nodes but now it takes 7 to 8 hours on 32 core HTCondor nodes . Are we sure all these HLT tests are properly utilizing the resources and are running in parallel ? |
Hmm, I see your point but would rather we close some old(er) CMSSW release cycles for good! Has this option been looked at? Once could always re-activate them in case of need (and then with HLT tests still there to make sure things work). |
We had disabled few of the old release cycles and reduce the build frequency for most of the production release cycles. So things are in better state now. There are still few old release cycles I am only wondering if HLT tests really need to run for all of the releases? It is enough to run these tests for those releases which were used by hlt? |
Hmm, we'd need to keep for all the releases used in data taking, and for which MC production is run, ie, in the end all releases which are kept alive (assuming that's the reason we keep releases alive?). |
closing this
|
HLT validation results on IB page are now marked failed if bot finds any tests exiting with non-zero status (
As reported #34231 (comment) ).
@Martin-Grunewald we are running HLT tests for all IBs (5.3.X to latest 12.0.X) and it is failing in few of the release cycles e.g.
5.3.X, 7.1.X, 8.0.X and 10.6.X
. Can we stop it for old release cycles?The text was updated successfully, but these errors were encountered: