Repository navigation
fs/azure: isolate the cross-storage copy test between parallel runs - #80
Merged
Merged
Conversation
The net6.0 and net8.0 runs shared the temp-storage container and the /1111.txt blob, so parallel runs failed with 412 ConditionNotMet or read each other's content. Use a unique container name, as the Amazon tests do.
This file contains hidden or 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
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.
File_CopyTo_File_DifferentStoragesused a fixedtemp-storagecontainer as the copy source.When the Azure tests ran without
-maxcpucount:1, thenet6.0andnet8.0runs wrote/1111.txtto the same container, so one of them failed with HTTP 412ConditionNotMetor read the other run's content.This PR uses a unique container name, as
WritableAmazonFileSystemTestsalready does.CI keeps
-maxcpucount:1for the Azure tests because they run much faster against Azurite that way.