-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
SyndicationFeed_Write_RSS_Atom test failing with "IOException : The file '/tmp/' already exists." #78454
Comments
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsBuild InformationBuild: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=84790 Error MessageFill the error message using known issues guidance. {
"ErrorMessage": "System.IO.IOException : The file '/tmp/' already exists.",
"BuildRetry": false
}
|
@akoeplinger did you see this for non-wasm case too? I thought this might be #73721 . |
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsBuild InformationBuild: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=84790 Stack trace:
Error MessageFill the error message using known issues guidance. {
"ErrorMessage": "System.IO.IOException : The file '/tmp/' already exists.",
"BuildRetry": false
} Report
Summary
|
@radical I thought I saw this outside of wasm but looks like I just looked at the wrong job. It does seem to show only on wasm. |
My guess is that it is #74855 because the assumption about failing and isDirError doesn't apply on wasm and it is probably that the filename is not unique enough |
and I think this can be closed as a dupe of that. |
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=84790
Build error leg or test failing: System.ServiceModel.Syndication.Tests.BasicScenarioTests.SyndicationFeed_Write_RSS_Atom
Pull request: #78424
Stack trace:
Error Message
Fill the error message using known issues guidance.
Report
Summary
The text was updated successfully, but these errors were encountered: