Fix fuzzers for .NET 8 SDK publish#80673
Conversation
dotnet publish does not allow publishing with an output path in the .NET 8 SDK. They failed this weekend's rolling runs so this change makes the build scripts specify the project to build.
ghost
assigned
|
Tagging subscribers to this area: @hoyosjs Issue Detailsdotnet publish does not allow publishing with an output path in the .NET 8 SDK. The pipelines failed today because of it (Antigen, Fuzzlyn). This change makes the build scripts specify the project to build. Context: dotnet/sdk#29065
|
jakobbotsch
added
area-CodeGen-coreclr
|
/azp run Antigen, Fuzzlyn |
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch, @kunalspathak Issue Detailsdotnet publish does not allow publishing with an output path in the .NET 8 SDK. The pipelines failed today because of it (Antigen, Fuzzlyn). This change makes the build scripts specify the project to build. Context: dotnet/sdk#29065
|
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
/azp run Fuzzlyn |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
cc @dotnet/jit-contrib PTAL @kunalspathak |
2 participants
dotnet publish does not allow publishing of solution files with an output path in the .NET 8 SDK. The pipelines failed today because of it (Antigen, Fuzzlyn). This change makes the build scripts specify the project to build.
Context: dotnet/sdk#29065