tests: add sleep after flow timeouts #180
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
For normal flow-mods we can use the barrier message to find out when the change has made it to the datapath. This isn't the case with timeouts, because the update isn't associated with any controller connection. When tests are run in short succession the timed out flow may still exist in the datapath when the next test starts.
|
ABAT: START_MERGE: Log file at http://vbs24/abat/2015.05.05.2142-m.oftest.master/abat.log |
|
ABAT: ACCEPT: Successfully merged In case you want to see the build log, check out : |
bsn-abat
pushed a commit
that referenced
this pull request
May 5, 2015
tests: add sleep after flow timeouts (#180)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reviewer: trivial
For normal flow-mods we can use the barrier message to find out when the
change has made it to the datapath. This isn't the case with timeouts, because
the update isn't associated with any controller connection. When tests are run
in short succession the timed out flow may still exist in the datapath when
the next test starts.