Skip to content
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

Removed confusing use of unscheduled term in global exception message #6027

Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
10 changes: 5 additions & 5 deletions FWCore/Framework/src/GlobalSchedule.h
Expand Up @@ -205,22 +205,22 @@ namespace edm {
catch (cms::Exception & ex) {
std::ostringstream ost;
if (T::begin_ && T::branchType_ == InRun) {
ost << "Calling beginRun";
ost << "Calling global beginRun";
}
else if (T::begin_ && T::branchType_ == InLumi) {
ost << "Calling beginLuminosityBlock";
ost << "Calling global beginLuminosityBlock";
}
else if (!T::begin_ && T::branchType_ == InLumi) {
ost << "Calling endLuminosityBlock";
ost << "Calling global endLuminosityBlock";
}
else if (!T::begin_ && T::branchType_ == InRun) {
ost << "Calling endRun";
ost << "Calling global endRun";
}
else {
// It should be impossible to get here ...
ost << "Calling unknown function";
}
ost << " for unscheduled module " << worker->description().moduleName()
ost << " for module " << worker->description().moduleName()
<< "/'" << worker->description().moduleLabel() << "'";
ex.addContext(ost.str());
ost.str("");
Expand Down