-
Notifications
You must be signed in to change notification settings - Fork 1.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
[net9.0] Move to rtm #25017
[net9.0] Move to rtm #25017
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are seeing similar weird workload errors here:
Using the rtm .NET SDK:
Writing workload pack installation record for Microsoft.NETCore.App.Runtime.AOT.osx-x64.Cross.android-arm64 version 9.0.0-rtm.24476.4...
##[error]Warning(0,0): Error : System.IO.FileNotFoundException: Workload version 9.0.100-rtm.24479.2 was not found.
1>Warning : Workload garbage collection failed with error : System.IO.FileNotFoundException: Workload version 9.0.100-rtm.24479.2 was not found. [/Users/runner/work/1/s/build-tools/create-packs/Microsoft.Android.Sdk.proj]
at Microsoft.NET.Sdk.WorkloadManifestReader.SdkDirectoryWorkloadManifestProvider.RefreshWorkloadManifests()
at Microsoft.NET.Sdk.WorkloadManifestReader.SdkDirectoryWorkloadManifestProvider..ctor(String sdkRootPath, String sdkVersion, Func`2 getEnvironmentVariable, String userProfileDir, String globalJsonPath, String workloadSetVersion)
at Microsoft.NET.Sdk.WorkloadManifestReader.SdkDirectoryWorkloadManifestProvider.ForWorkloadSet(String sdkRootPath, String sdkVersion, String userProfileDir, String workloadSetVersion)
at Microsoft.DotNet.Workloads.Workload.Install.WorkloadResolverFactory.CreateForWorkloadSet(String dotnetPath, String sdkVersion, String userProfileDir, String workloadSetVersion)
at Microsoft.DotNet.Workloads.Workload.Install.WorkloadGarbageCollector.GarbageCollectWorkloadManifestsAndPacks()
at Microsoft.DotNet.Workloads.Workload.Install.WorkloadGarbageCollector.Collect()
at Microsoft.DotNet.Workloads.Workload.Install.FileBasedInstaller.GarbageCollect(Func`2 getResolverForWorkloadSet, Nullable`1 offlineCache, Boolean cleanAllPacks)
at Microsoft.DotNet.Workloads.Workload.Install.WorkloadInstallCommand.TryRunGarbageCollection(IInstaller workloadInstaller, IReporter reporter, VerbosityOptions verbosity, Func`2 getResolverForWorkloadSet, Nullable`1 offlineCache).
Successfully installed workload(s) android.
I think the workload installed successfully, but then a GC warning made it a non-zero exit code?
I think @marcpopMSFT or @dsplaisted mentioned they are fixing something related to rtm branding & workloads?
Yes, this should be fixed with this PR: dotnet/sdk#43797 Garbage collection is failing, which for most workload commands is reported as a warning but the command completes successfully. For |
Ok, I see why it failed, we run some |
The fix has been merged. If you need a workaround before it flows, you could delete the |
I think there is a build, trying it here:
|
Yeah @Redth the issue is back here with RTM
|
/rebase |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
Description of Change
Move net9 to rtm versions