Skip to content

Commit e2673ce

Browse files
committed
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 e2673ce

1 file changed

Lines changed: 4 additions & 5 deletions

File tree

‎Framework/src/TaskRunner.cxx‎

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -416,11 +416,10 @@ 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 "
421-
<< "(" << mTimekeeper->getValidity().getMin() << ", " << mTimekeeper->getValidity().getMax() << "), "
422-
<< "(" << mTimekeeper->getSampleTimespan().getMin() << ", " << mTimekeeper->getSampleTimespan().getMax() << "), "
423-
<< "(" << mTimekeeper->getTimerangeIdRange().getMin() << ", " << mTimekeeper->getTimerangeIdRange().getMax() << ")" << ENDM;
419+
ILOG(Info, Devel) << "The objects validity is " //
420+
<< "(" << mTimekeeper->getValidity().getMin() << ", " << mTimekeeper->getValidity().getMax() << "), "
421+
<< "(" << mTimekeeper->getSampleTimespan().getMin() << ", " << mTimekeeper->getSampleTimespan().getMax() << "), "
422+
<< "(" << mTimekeeper->getTimerangeIdRange().getMin() << ", " << mTimekeeper->getTimerangeIdRange().getMax() << ")" << ENDM;
424423
mTask->endOfCycle();
425424

426425
if (mCycleNumber == 0) { // register at the end of the first cycle

0 commit comments

Comments
 (0)