-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release/7.0] Properly handle filesizes larger than 8 Gb #76756
Conversation
Tagging subscribers to this area: @dotnet/area-system-io Issue DetailsBackport of #76707 to release/7.0 /cc @jozkee Customer ImpactTestingRiskIMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.
|
Approved by Tactics via email. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
/azp run runtime-libraries-coreclr outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
CI failures unrelated. Approved and signed off. Ready to merge. |
Backport of #76707 to release/7.0
/cc @jozkee
Customer Impact
Testing
size
= 8,589,934,591) on all formats.size
.Risk
New feature, no regression involved. There's risk on the newly added tests since those create 8 Gb files, but they are marked as outerloop and parallelization is disabled.
IMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.