Updated File Progress Receiver Tests #7961
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
alzimmermsft
requested review from
gapra-msft,
jaschrep-msft,
rickle-msft and
sima-zhu
as code owners
|
/azp run java - storage - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run java - storage - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run java - storage - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
gapra-msft
approved these changes
Feb 4, 2020
|
/azp run java - storage - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
alzimmermsft
force-pushed
the
AzStorage_LiveTestFailures
branch
from
27a4f38 to
ae21b49
Compare
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.
Updated the
BlobAPITestandEncryptedBlockBlobAPITestDownload file progress receivertests to handle the case when there are empty buffers in the reactive stream after the full download size has reached completion. The test now validates that there is at least one report with the expected file size and there are zero reports which are greater than the expected size.