-
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
Add temporary failure element to Framework Job Report #41124
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41124/34762
|
A new Pull Request was created by @Dr15Jones (Chris Jones) for master. It involves the following packages:
@cmsbuild, @smuzaffar, @Dr15Jones, @makortel can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
static char const* const kJobReportEndElement = "</FrameworkJobReport>\n"; | ||
static constexpr int kEndElementSize = 22; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be possible and feasible to use std::string_view
and take the number of elements from its size()
(which, I see, should be constexpr
)?
if ((endpos - pos) > kEndElementSize) { | ||
//need to add some padding so use a comment element | ||
auto padding = (endpos - pos) - (kEndElementSize + kMinSizeOfComment); | ||
*(impl_->ost_) << "<!--"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add a comment here explaining briefly why an XML comment is used instead of white space? (to remind us the next time we need to look at this code)
Not really part of this PR, but while we are here, I looked where cmssw/FWCore/MessageLogger/src/JobReport.cc Lines 668 to 685 in 4c4bee9
cmssw/FWCore/MessageLogger/src/JobReport.cc Lines 687 to 706 in 4c4bee9
do not lock the mutex. Currently they are called only in ActivityRegistry 's postEndJob signal that we seem to be calling serially. Should we nevertheless lock the mutex in these functions?
|
-1 Failed Tests: UnitTests The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: You can see more details here: Unit TestsI found errors in the following unit tests: ---> test PrimaryVertex had ERRORS ---> test testPVPlotting had ERRORS ---> test trackerMaterialAnalysisPlots had ERRORS ---> test createDBObjecs had ERRORS and more ... Comparison SummarySummary:
|
Until the job report finishes, we add a FrameworkError element to denote that if the job suddenly ends the error will be present. When job completes successfully or with another error, that temporary element is not written. The new error was added to edm::errors.
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41124/34821
|
Pull request #41124 was updated. @cmsbuild, @smuzaffar, @Dr15Jones, @makortel can you please check and sign again. |
@cmsbuild, please test |
Regarding #41124 (comment), for future reference, we decided not to add |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-a928c2/31569/summary.html Comparison SummarySummary:
|
+core |
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. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Until the job report finishes, we add a FrameworkError element to denote that if the job suddenly ends the error will be present. When job completes successfully or with another error, that temporary element is not written.
The new error was added to edm::errors.
PR validation:
Code compiles and framework unit tests pass.