[0.2.x] REP-64 Fix for itest timing issue #72
Closed
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
* Suppress hadoop-auth cve * Remove beta from navbar title
Added Dominion support. Updated itests to use Dominion. Added instructions to comment on PR for build starting and status Updated DDF to 2.13.8 and removed invalid test case REP-64 Updated codice-test to 0.7
…updated DDF to the latest.
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.
What does this PR do?
It fixes the timing issue during integration testing by updating the codice-test and ddf dependencies to take advantage of their fix for the issue.
Who is reviewing it (please choose AT LEAST two reviewers that need to approve the PR before it can get merged)?
@peterhuffer @kcover @clockard @mcalcote
How should this be tested? (List steps with links to updated documentation)
build passing
Any background context you want to provide?
What are the relevant tickets?
Fixes #64
Screenshots (if appropriate)
Checklist: