[RF] Avoid deprecation warnings when building RooFit tests - #23274
Open
guitargeek wants to merge 1 commit into
Open
[RF] Avoid deprecation warnings when building RooFit tests#23274guitargeek wants to merge 1 commit into
guitargeek wants to merge 1 commit into
Conversation
Follows up on 177d13d, bringing back the good old `ROOFIT_BUILDS_ITSELF` macro for this development cycle to avoid compilation warnings when building RooFit's own unit tests.
guitargeek
added
in:RooFit
pr:emergency🚨
Test Results 23 files 23 suites 3d 18h 13m 48s ⏱️ For more details on these failures, see this check. Results for commit a4d1a96. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follows up on 177d13d, bringing back the good old
ROOFIT_BUILDS_ITSELFmacro for this development cycle to avoid compilation warnings when building RooFit's own unit tests.Emergency PR because the warnings make Debian 13 red in the CI, because of the
dev=ONflag of that configuration. Once again, I didn't catch it in the original PR, because the Debian 13 build in that PR was green. I think it's a problem with the CI configuration.