Fix flaky pauseAndResume_ObjectNotChanged_shouldResumeDownload integ test #6554
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.



Fix flaky pauseAndResume_ObjectNotChanged_shouldResumeDownload integ test
Motivation and Context
This integ test can fail when trying to verify the number of bytes transferred with
assertThat(resumedFileDownload.progress().snapshot().totalBytes()).hasValue(expectedBytesTransferred)after resume is called with errors like:In these cases the actual bytes transferred on the resumed file download is less than expected because additional bytes are flushed to the file AFTER pause is called and not counted in the
bytesTransferredstat. However, the client handles this correctly and will write the correct data to the file (we verify this withassertThat(path.toFile()).hasSameBinaryContentAs(sourceFile);).Modifications
Testing
re-run integ test many times without failure.
Screenshots (if appropriate)
Types of changes
Checklist
mvn installsucceedsscripts/new-changescript and following the instructions. Commit the new file created by the script in.changes/next-releasewith your changes.License