Project

General

Profile

Bug #2037

Unstable FwNccStrategy/FavorRespondingUpstream test case

Added by Alex Afanasyev almost 5 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
IntegTests
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
1.00 h

Description

Test case FwNccStrategy/FavorRespondingUpstream has been a reason for multiple retriggering on jenkins buildbot.

If the test relies on specific timing, the test should use large time values, so it is more stable in overloaded environments, like our Jenkins.

These are details for the failure:

Entering test suite "FwNccStrategy"
Entering test case "FavorRespondingUpstream"
1412788935.714850 INFO: [StrategyChoice] Set default strategy /localhost/nfd/strategy/best-route/%FD%02
1412788935.718003 INFO: [StrategyChoiceEntry] Set strategy /localhost/nfd/strategy/best-route/%FD%02 for / prefix
1412788935.721408 INFO: [FaceTable] Added face id=256 remote=dummy:// local=dummy://
1412788935.722378 INFO: [FaceTable] Added face id=257 remote=dummy:// local=dummy://
1412788935.723358 INFO: [FaceTable] Added face id=258 remote=dummy:// local=dummy://
1412788935.724426 INFO: [StrategyChoiceEntry] Set strategy /localhost/nfd/strategy/ncc/%FD%01/tester for / prefix
../tests/daemon/fw/ncc-strategy.cpp:79: fatal error in "FavorRespondingUpstream": critical check strategy->m_sendInterestHistory.size() == 1 failed [2 != 1]
Leaving test case "FavorRespondingUpstream"; testing time: 4759mks

History

#1 Updated by Alex Afanasyev almost 5 years ago

  • Tracker changed from Task to Bug

#2 Updated by Junxiao Shi almost 5 years ago

  • Status changed from New to In Progress
  • Priority changed from Normal to High
  • Estimated time set to 1.00 h

#3 Updated by Junxiao Shi almost 5 years ago

  • Status changed from In Progress to Code review
  • % Done changed from 0 to 100

It's infeasible to use larger durations due to the design of NccStrategy (not the test case).

I'm optimizing the test case by using operation-count based LimitedIo runs.

#4 Updated by Junxiao Shi almost 5 years ago

  • Status changed from Code review to Resolved

A fix is merged. This bug can close after 7 days if this test case does not fail on Jenkins.

#5 Updated by Junxiao Shi almost 5 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF