Skip to content

fs/azure: isolate the cross-storage copy test between parallel runs - #80

Merged
rameel merged 1 commit into
mainfrom
fs/azure/isolate-copy-test
Nov 16, 2026
Merged

rameel merged 1 commit into
mainfrom
fs/azure/isolate-copy-test

Conversation

@rameel

@rameel rameel commented Nov 16, 2026 •

Copy link
Copy Markdown
Owner

File_CopyTo_File_DifferentStorages used a fixed temp-storage container as the copy source.
When the Azure tests ran without -maxcpucount:1, the net6.0 and net8.0 runs wrote /1111.txt to the same container, so one of them failed with HTTP 412 ConditionNotMet or read the other run's content.

This PR uses a unique container name, as WritableAmazonFileSystemTests already does.

CI keeps -maxcpucount:1 for the Azure tests because they run much faster against Azurite that way.

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.
@rameel
rameel merged commit 10ad5bc into main Nov 16, 2026
4 checks passed
@rameel
rameel deleted the fs/azure/isolate-copy-test branch November 16, 2026 17:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant