Repository navigation
[PERF] Fix mono dotnet creation - #78257
Conversation
ghost
added
the 
|
Tagging subscribers to this area: @hoyosjs Issue DetailsThe create mono dotnet job is failing due to mismatches in the command line used, this fixes that. Here is a test run with the changes to the mono dotnet job: https://dev.azure.com/dnceng/internal/_build/results?buildId=2043117&view=results. This fixes dotnet/performance#2719 for main. The current reason for this problem seems to be that main is still using net7.0 sdk versions and net7.0 targetting in the build-job.yml for building coreclr and libraries. While what we run is still main, some of the names of the items mismatch, and in this case that is net7.0 being in the bin output instead of net8.0.
|
This reverts commit 74c8fd3.
cincuranet
left a comment
cincuranet
left a comment
There was a problem hiding this comment.
The changes in commands LGTM.
…ues do currently need to be hardcoded.
|
Successful perf pipeline testing run: https://dev.azure.com/dnceng/internal/_build/results?buildId=2045192&view=results |
This reverts commit d7e941e.
|
Pipeline is green. Merging per @LoopedBard3's request. |
The create mono dotnet job is failing due to mismatches in the command line used, this fixes that. Here is a test run with the changes to the mono dotnet job: https://dev.azure.com/dnceng/internal/_build/results?buildId=2043117&view=results. This fixes dotnet/performance#2719 for main.
The current reason for this problem seems to be that main is still using net7.0 sdk versions and net7.0 targetting in the build-job.yml for building coreclr and libraries. While what we run is still main, some of the names of the items mismatch, and in this case that is net7.0 being in the bin output instead of net8.0.