Skip to content

Commit 3425eef

Browse files
authored
Stop verbose logging of object validity in async QC
The mechanism was validated already some time ago, there is no need for separate behaviour anymore.
1 parent db03f45 commit 3425eef

1 file changed

Lines changed: 1 addition & 2 deletions

File tree

‎Framework/src/TaskRunner.cxx‎

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -416,8 +416,7 @@ void TaskRunner::finishCycle(DataAllocator& outputs)
416416
{
417417
ILOG(Debug, Support) << "Finish cycle " << mCycleNumber << ENDM;
418418
// in the async context we print only info/ops logs, it's easier to temporarily elevate this log
419-
((mDeploymentMode == DeploymentMode::Grid) ? ILOG(Info, Ops) : ILOG(Info, Devel)) //
420-
<< "The objects validity is "
419+
ILOG(Info, Devel) << "The objects validity is " //
421420
<< "(" << mTimekeeper->getValidity().getMin() << ", " << mTimekeeper->getValidity().getMax() << "), "
422421
<< "(" << mTimekeeper->getSampleTimespan().getMin() << ", " << mTimekeeper->getSampleTimespan().getMax() << "), "
423422
<< "(" << mTimekeeper->getTimerangeIdRange().getMin() << ", " << mTimekeeper->getTimerangeIdRange().getMax() << ")" << ENDM;

0 commit comments

Comments
 (0)