-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
error MSB3030: (NETCORE_ENGINEERING_TELEMETRY=Build) Could not copy the file #42964
Comments
@marcpopMSFT is this a known problem in the sdk tests? |
@lewing yes it is. A workaround was put in two years ago for this but it was fairly hacky. @MiYanni undid that workaround on the path to simplifying the test infrastructure but that work is not done yet so this issue is still in play. We may want to think about a temporary fix to make sure this isn't impacting builds. |
I took another look at the binlog and I tracked down the potential issue. These files aren't being included in the default item include like I thought but because of an explicit include in the test directory.build.targets. I'm going to remove that include entirely and see what fails. Regardless, we should not copy the test assets into every single test publish folder as that's a lot of duplication for no reason. |
Should be fixed in 9.0.1xx now with my linked PR. |
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=785882
Build error leg or test failing: Build / FullFramework: windows (x64) / Build
Pull request: #42833
Error Message
Fill the error message using step by step known issues guidance.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=785882
Error message validated:
[error MSB3030: (NETCORE_ENGINEERING_TELEMETRY=Build) Could not copy the file
]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 8/23/2024 3:00:11 AM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: