-
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
error CS0006: Metadata file '.../maccatalyst-arm64/StartupHookForFunctionalTest.dll' could not be found #80976
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @directhex Issue Details
|
@steveisok @lambdageek runtime/eng/testing/tests.ioslike.targets Lines 168 to 184 in da03f60
$(OutDir)
Afterwards, the |
@mdh1418 can we skip this test until there's a fix? |
Yeah, I can skip it. I think the problem inherently because this test has a ProjectReference runtime/src/tests/FunctionalTests/iOS/Simulator/StartupHook/iOS.Simulator.StartupHook.Test.csproj Line 19 in da03f60
but its not clear to me how this ends up with a reference to /Users/mihw/runtime/runtime_ios/artifacts/bin/StartupHookForFunctionalTest/release/net8.0/iossimulator-arm64/StartupHookForFunctionalTest.dll in CoreCompile d as opposed to the libraries tests which also have ProjectReference but dont have this problem.
|
ProjectReferences should work. |
Maybe the ProjectReference should be Private? |
We were deleting that directory as a means to help conserve disk space, but upon some investigations in #82313 (comment), we still have plenty of disk space left even if we retain |
@lambdageek @steveisok
_CopyTestArchive and removing the output directory before we actually try to compile the actual project in CoreCompile
|
runtime-extra-platforms
fails on ios/tvos/maccatalyst with:e.g. https://dev.azure.com/dnceng-public/public/_build/results?buildId=144305&view=logs&jobId=cbf7f906-06a1-5744-2b19-594b1486a781&j=07effcfd-c63d-5008-e811-03b29530f5cb&t=46984e67-96b8-5591-f4ad-dfc0b5406724
The text was updated successfully, but these errors were encountered: