-
Notifications
You must be signed in to change notification settings - Fork 477
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
GitHub Actions Failing to Build .NET 9.0 Project #562
Comments
I may get a similar issue (?) When I upgrade {
"sdk": {
"version": "8.0.404",
"quality": "release"
}
} to {
"sdk": {
"version": "9.0.100",
"quality": "release"
}
} I got error in my build: Unhandled exception: System.Exception: The build host could not be found at '/usr/share/dotnet/sdk/9.0.100/DotnetTools/dotnet-format/BuildHost-net472/Microsoft.CodeAnalysis.Workspaces.MSBuild.BuildHost.exe'
at Microsoft.CodeAnalysis.MSBuild.BuildHostProcessManager.AssertBuildHostExists(String buildHostPath)
at Microsoft.CodeAnalysis.MSBuild.BuildHostProcessManager.GetDotNetFrameworkBuildHostPath()
at Microsoft.CodeAnalysis.MSBuild.BuildHostProcessManager.CreateMonoBuildHostStartInfo()
at Microsoft.CodeAnalysis.MSBuild.BuildHostProcessManager.GetBuildHostAsync(BuildHostProcessKind buildHostKind, CancellationToken cancellationToken)
at Microsoft.CodeAnalysis.MSBuild.BuildHostProcessManager.GetBuildHostWithFallbackAsync(BuildHostProcessKind buildHostKind, String projectOrSolutionFilePath, CancellationToken cancellationToken)
at Microsoft.CodeAnalysis.MSBuild.MSBuildProjectLoader.Worker.LoadProjectFileInfosAsync(String projectPath, DiagnosticReportingOptions reportingOptions, CancellationToken cancellationToken)
at Microsoft.CodeAnalysis.MSBuild.MSBuildProjectLoader.Worker.LoadProjectInfosFromPathAsync(String projectPath, DiagnosticReportingOptions reportingOptions, CancellationToken cancellationToken)
at Microsoft.CodeAnalysis.MSBuild.MSBuildProjectLoader.Worker.LoadAsync(CancellationToken cancellationToken)
at Microsoft.CodeAnalysis.MSBuild.MSBuildProjectLoader.LoadSolutionInfoAsync(String solutionFilePath, IProgress`1 progress, ILogger msbuildLogger, CancellationToken cancellationToken)
at Microsoft.CodeAnalysis.MSBuild.MSBuildProjectLoader.LoadSolutionInfoAsync(String solutionFilePath, IProgress`1 progress, ILogger msbuildLogger, CancellationToken cancellationToken)
at Microsoft.CodeAnalysis.MSBuild.MSBuildWorkspace.OpenSolutionAsync(String solutionFilePath, ILogger msbuildLogger, IProgress`1 progress, CancellationToken cancellationToken)
at Microsoft.CodeAnalysis.Tools.Workspaces.MSBuildWorkspaceLoader.LoadAsync(String solutionOrProjectPath, WorkspaceType workspaceType, String binaryLogPath, Boolean logWorkspaceWarnings, ILogger logger, CancellationToken cancellationToken)
at Microsoft.CodeAnalysis.Tools.CodeFormatter.OpenMSBuildWorkspaceAsync(String solutionOrProjectPath, WorkspaceType workspaceType, Boolean noRestore, Boolean requiresSemantics, String binaryLogPath, Boolean logWorkspaceWarnings, ILogger logger, CancellationToken cancellationToken)
at Microsoft.CodeAnalysis.Tools.CodeFormatter.FormatWorkspaceAsync(FormatOptions formatOptions, ILogger logger, CancellationToken cancellationToken, String binaryLogPath)
at Microsoft.CodeAnalysis.Tools.FormatCommandCommon.FormatAsync(FormatOptions formatOptions, ILogger`1 logger, CancellationToken cancellationToken)
at Microsoft.CodeAnalysis.Tools.Commands.RootFormatCommand.FormatCommandDefaultHandler.InvokeAsync(ParseResult parseResult, CancellationToken cancellationToken)
at System.CommandLine.Invocation.InvocationPipeline.InvokeAsync(ParseResult parseResult, CancellationToken cancellationToken) |
Hello @ZjzMisaka, Thank you for creating this issue and we will look into it :) |
Hi, thank you for the help, is there any progress, or something need my help? |
Hello @ZjzMisaka, Workflow Configuration: steps:
1.The specified Target Framework Monikers (TFMs) indicate compatibility with multiple .NET versions. For more details, refer to the Select which .NET version to use - .NET | Microsoft Learn. Please let us know if you have any further questions or need additional support |
@mahalakshmi-rekadi Thank you, your suggestion works well. However, I’d like to know if the ubuntu-latest runner will support .NET 9.0 in the near future? |
(I saw @ZjzMisaka 's change at https://github.com/ZjzMisaka/PowerThreadPool/pull/81/files and succeed. Strange, mine still failed, I will test more and if still no luck, will create a new ticket as @ZjzMisaka 's original question has been resolved. Thanks!) |
@hongbo-miao I'm not sure but maybe you should try to add this?
|
(Thanks @ZjzMisaka @mahalakshmi-rekadi for helping! Glad @ZjzMisaka 's original issue has been resolved. However, I was happy too early as I found my issue is complete different. I posted details at #563) |
Hello @ZjzMisaka , The timeline for native support of .NET 9.0 on ubuntu-latest is not specified. If .NET 9.0 support becomes available, you can re-run the failed Actions to see if they pass. For now, continue specifying the .NET 9.0 SDK version in your workflow as recommended. To stay updated on supported software versions for GitHub Actions runners, check these resources: GitHub Actions Runner Images Please feel free to reach out if you have any concerns or need additional assistance. Thanks! |
@mahalakshmi-rekadi Hi,
Does that mean ubuntu-latest does not natively support .NET 6.0 now? should I edit test.yml again, or just wait? |
Description:
I recently updated my project to target .NET 9.0 after its release. I modified the csproj file to set the TargetFramework to .NET 9.0 and successfully built the project on my local machine. However, after committing the changes, the GitHub Actions workflow fails during the build step with the following error:
This suggests that the version of the .NET SDK being used in the GitHub Actions environment does not yet support .NET 9.0.
Questions:
Task version:
actions/setup-dotnet@v3
Platform:
Runner type:
Repro steps:
https://github.com/ZjzMisaka/PowerThreadPool/blob/main/.github/workflows/test.yml
Expected behavior:
Successfully build
Actual behavior:
Build step with the following error:
The text was updated successfully, but these errors were encountered: