common, include, osd: compile with fmt v9#47830
Merged
Conversation
ronen-fr
requested changes
Aug 27, 2022
Contributor
ronen-fr
left a comment
There was a problem hiding this comment.
LGTM (LVGTM...) apart from that extra #include
Contributor
|
commit message description? |
so we can use the formatter defined for `entity_name_t`. in fmtlib v9, it is required to define a specialization for the formatted type even the type has an override of operator<<(). now that we already have a formatter for `entity_name_t`, let's just use it. this change should address the FTBFS when building with fmtlib v9. Signed-off-by: Kefu Chai <tchaikov@gmail.com>
so we can use the formatter defined for `LogEntry` in fmtlib v9. in this new version of fmtlib, it is required to define a specialization for the formatted type even when it comes to the types with an override of operator<<(). since we already have an override for `LogEntry`, let's define the specialization for `fmt::formatter<LogEntry>`. this change should address the FTBFS when building with fmtlib v9. Signed-off-by: Kefu Chai <tchaikov@gmail.com>
so these formatters can be used in methods with `const` specifier. Signed-off-by: Kefu Chai <tchaikov@gmail.com>
2da0585 to
3d7a895
Compare
Contributor
Author
@ronen-fr could you please be more specific? i think each commit in this PR has commit message. if any of them is missing or just wrong, please let me know. |
Contributor
Author
|
@ronen-fr fixed and repushed. could you take another look? |
Contributor
|
Sorry - meant the PR message, not the specific commits. |
ronen-fr
approved these changes
Aug 27, 2022
Contributor
Author
|
jenkins test make check |
Contributor
|
jenkins retest this please |
Contributor
|
jenkins test api |
1 similar comment
Contributor
Author
|
jenkins test api |
sseshasa
added a commit
to sseshasa/ceph
that referenced
this pull request
Feb 5, 2024
…try> The Ceph cluster logs were missing the string equivalent [INF|WRN|ERR|DBG] representation of the 'prio' field. This was broken since the introduction of commit 2901943 of PR: ceph#47830. This probably caused false positives in teuthology testing and particularly for those tests that check for cluster badness by parsing the cluster logs. The fix involves adding a static helper function to the LogEntry struct. This function returns the string appropriate representation of the log level similar to the operator<<() for LogEntry. Signed-off-by: Sridhar Seshasayee <sseshasa@redhat.com> Fixes: https://tracker.ceph.com/issues/64314
14 tasks
sseshasa
added a commit
to sseshasa/ceph
that referenced
this pull request
Feb 5, 2024
…try> The Ceph cluster logs were missing the string equivalent [INF|WRN|ERR|DBG] representation of the 'prio' field. This was broken since the introduction of commit 2901943 of PR: ceph#47830. This probably caused false positives in teuthology testing and particularly for those tests that check for cluster badness by parsing the cluster logs. The fix involves adding a static helper function to the LogEntry struct. This function returns the string appropriate representation of the log level similar to the operator<<() for LogEntry. Signed-off-by: Sridhar Seshasayee <sseshasa@redhat.com> Fixes: https://tracker.ceph.com/issues/64314
sseshasa
added a commit
to sseshasa/ceph
that referenced
this pull request
Feb 5, 2024
…try> The Ceph cluster logs were missing the string equivalent [INF|WRN|ERR|DBG] representation of the 'prio' field. This was broken since the introduction of commit 2901943 of PR: ceph#47830. This probably caused false positives in teuthology testing and particularly for those tests that check for cluster badness by parsing the cluster logs. The fix involves adding a static helper function to the LogEntry struct. This function returns the string appropriate representation of the log level similar to the operator<<() for LogEntry. Fixes: https://tracker.ceph.com/issues/64314 Signed-off-by: Sridhar Seshasayee <sseshasa@redhat.com>
14 tasks
bill-scales
pushed a commit
to bill-scales/ceph
that referenced
this pull request
Mar 13, 2024
…try> The Ceph cluster logs were missing the string equivalent [INF|WRN|ERR|DBG] representation of the 'prio' field. This was broken since the introduction of commit 2901943 of PR: ceph#47830. This probably caused false positives in teuthology testing and particularly for those tests that check for cluster badness by parsing the cluster logs. The fix involves adding a static helper function to the LogEntry struct. This function returns the string appropriate representation of the log level similar to the operator<<() for LogEntry. Fixes: https://tracker.ceph.com/issues/64314 Signed-off-by: Sridhar Seshasayee <sseshasa@redhat.com>
sseshasa
added a commit
to sseshasa/ceph
that referenced
this pull request
Mar 26, 2024
…try> The Ceph cluster logs were missing the string equivalent [INF|WRN|ERR|DBG] representation of the 'prio' field. This was broken since the introduction of commit 2901943 of PR: ceph#47830. This probably caused false positives in teuthology testing and particularly for those tests that check for cluster badness by parsing the cluster logs. The fix involves adding a static helper function to the LogEntry struct. This function returns the string appropriate representation of the log level similar to the operator<<() for LogEntry. Fixes: https://tracker.ceph.com/issues/64314 Signed-off-by: Sridhar Seshasayee <sseshasa@redhat.com> (cherry picked from commit 0bd01b9)
mkogan1
pushed a commit
to mkogan1/ceph
that referenced
this pull request
Aug 7, 2024
…try> The Ceph cluster logs were missing the string equivalent [INF|WRN|ERR|DBG] representation of the 'prio' field. This was broken since the introduction of commit 2901943 of PR: ceph#47830. This probably caused false positives in teuthology testing and particularly for those tests that check for cluster badness by parsing the cluster logs. The fix involves adding a static helper function to the LogEntry struct. This function returns the string appropriate representation of the log level similar to the operator<<() for LogEntry. Fixes: https://tracker.ceph.com/issues/64314 Signed-off-by: Sridhar Seshasayee <sseshasa@redhat.com> (cherry picked from commit 0bd01b9)
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
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.
Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "pacific"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
Checklist
Show available Jenkins commands
jenkins retest this pleasejenkins test classic perfjenkins test crimson perfjenkins test signedjenkins test make checkjenkins test make check arm64jenkins test submodulesjenkins test dashboardjenkins test dashboard cephadmjenkins test apijenkins test docsjenkins render docsjenkins test ceph-volume alljenkins test ceph-volume toxjenkins test windows