Reduce severity of some logging messages

This commit is contained in:
JoelKatz
2015-05-12 09:33:06 -07:00
committed by Vinnie Falco
parent 688f8c5f3f
commit a15785eb64
4 changed files with 4 additions and 4 deletions

View File

@@ -1460,7 +1460,7 @@ uint256 Ledger::getLedgerHash (std::uint32_t ledgerIndex)
if ((ledgerIndex & 0xff) != 0)
{
WriteLog (lsWARNING, Ledger) << "Can't get seq " << ledgerIndex
WriteLog (lsDEBUG, Ledger) << "Can't get seq " << ledgerIndex
<< " from " << mLedgerSeq << " past";
return uint256 ();
}

View File

@@ -335,7 +335,7 @@ TER PathState::pushNode (
node.issue_.currency);
if (-saOwed >= saLimit)
{
WriteLog (lsWARNING, RippleCalc) <<
WriteLog (lsDEBUG, RippleCalc) <<
"pushNode: dry:" <<
" saOwed=" << saOwed <<
" saLimit=" << saLimit;

View File

@@ -322,7 +322,7 @@ TER PathCursor::deliverNodeForward (
{
// Offer became unfunded.
WriteLog (lsWARNING, RippleCalc)
WriteLog (lsDEBUG, RippleCalc)
<< "deliverNodeForward: unfunded:"
<< " saOutPassAct=" << saOutPassAct
<< " saOutFunded=" << saOutFunded;

View File

@@ -818,7 +818,7 @@ public:
{
if (slot->connectivityCheckInProgress)
{
if (m_journal.warning) m_journal.warning << beast::leftw (18) <<
if (m_journal.debug) m_journal.debug << beast::leftw (18) <<
"Logic testing " << ep.address << " already in progress";
continue;
}