Skip to content
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

Bump main version to 9.0-alpha1 #90558

Merged
merged 38 commits into from
Aug 23, 2023
Merged

Bump main version to 9.0-alpha1 #90558

merged 38 commits into from
Aug 23, 2023

Conversation

carlossanlop
Copy link
Member

🎉

@ghost
Copy link

ghost commented Aug 15, 2023

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

🎉

Author: carlossanlop
Assignees: carlossanlop
Labels:

area-Infrastructure

Milestone: 9.0.0

@carlossanlop
Copy link
Member Author

@dotnet/ncl or @ViktorHofer do you know how to address the Quic failure message about opting into preview features?:

src/libraries/System.Net.Http/src/System/Net/Http/SocketsHttpHandler/Http3Connection.cs(29,37): error CA2252: (NETCORE_ENGINEERING_TELEMETRY=Build) '_activeRequests''s type contains the preview type 'QuicStream' and requires opting into preview features. See https://aka.ms/dotnet-warnings/preview-features for more information. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2252)

@wfurt
Copy link
Member

wfurt commented Aug 15, 2023

Strange, HTTP already has the preview feature set:

<EnablePreviewFeatures>true</EnablePreviewFeatures>

Perhaps something in the SDK?

BTW This may also break the Enterprise pipeline - at least it always did in the past.

@jkoritzinsky
Copy link
Member

EnablePreviewFeatures has an interesting behavior that it only works on the most current TFM. Looks like we might need some other solution here.

@wfurt
Copy link
Member

wfurt commented Aug 15, 2023

removing RequiresPreviewFeaturesAttribute from Quic for now? I would hope nobody would use 9.0 in production yet.

@jkoritzinsky
Copy link
Member

Maybe manually including the attribute in the .NET 8 build (instead of using the SDK property) would work.

@antonfirsov
Copy link
Member

/azp-run runtime-libraries stress-http

@antonfirsov
Copy link
Member

/azp-run runtime-libraries enterprise-linux

@jkoritzinsky
Copy link
Member

@carlossanlop @wfurt I looked more into the failure. Here's whats happening:

  • We have infrastructure to automatically say that for <MajorVersion>N</MajorVersion>, the latest TFM is netN.0.
  • This PR updates MajorVersion to 9.
  • This PR does not update NetCoreAppCurrent to net9.0.
  • As a result, System.Net.Http is building for net8.0.
  • The SDK isn't applying the EnablePreviewFeatures attribute as net8.0 is no longer the "latest TFM".

There are two possible solutions:

  • Manually include the EnablePreviewFeatures attribute until we change NetCoreAppCurrent.
  • Change NetCoreAppCurrent (and NetCoreAppMinimum and NetCoreAppPrevious as well) now and face the problems that come with that now.

@carlossanlop which would you rather do? I'd prefer the second option personally.

@jkoritzinsky
Copy link
Member

I've started down the path of the second option locally. I'll try to finish it up tomorrow so I can push it out (just fixing up APICompat baselining).

…void regressions in .NET 8.0 targets and clean up .NET 8->.NET 9 API compat baselining.
@jkoritzinsky
Copy link
Member

PR with the TFM upgrade is at #90880

Thank you so much, @jkoritzinsky, that is a huge contribution. I think it's best to send it separately.

I agree. This PR only has the changes required for the rebranding, not the TFM upgrade.

@@ -139,6 +139,48 @@
<Left>ref/net8.0/System.Linq.Expressions.dll</Left>
<Right>lib/net8.0/System.Linq.Expressions.dll</Right>
</Suppression>
<Suppression>
Copy link
Member

@ViktorHofer ViktorHofer Aug 21, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These changes should be reverted. Same for the test binary file below.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The build fails without these two changes.

@radical
Copy link
Member

radical commented Aug 21, 2023

New sdk error on windows:

EXEC : error : dotnet-install: Failed to check the disk space. Installation will continue, but it may fail if you do not have [D:\a\_work\1\s\src\mono\wasm\Wasm.Build.Tests\Wasm.Build.Tests.csproj]
##[error]EXEC(0,0): error : (NETCORE_ENGINEERING_TELEMETRY=Build) dotnet-install: Failed to check the disk space. Installation will continue, but it may fail if you do not have
   enough disk space.
  dotnet-install: Extracting the archive.

The log doesn't show the exit code. I'll check locally.

@radical
Copy link
Member

radical commented Aug 22, 2023

New sdk error on windows:

EXEC : error : dotnet-install: Failed to check the disk space. Installation will continue, but it may fail if you do not have [D:\a\_work\1\s\src\mono\wasm\Wasm.Build.Tests\Wasm.Build.Tests.csproj]
##[error]EXEC(0,0): error : (NETCORE_ENGINEERING_TELEMETRY=Build) dotnet-install: Failed to check the disk space. Installation will continue, but it may fail if you do not have
   enough disk space.
  dotnet-install: Extracting the archive.

The log doesn't show the exit code. I'll check locally.

I'm not sure what is wrong here. The dotnet-install.ps1 script uses Write-Warning to emit the message, and this script is being run with Exec msbuild task with IgnoreStandardErrorWarningFormat="true". I don't know how it is becoming an error. The task doesn't even seem to fail the build, and instead the whole build completes, and then msbuild shows the error at the end.

Update: the warning is emitted if the powershell version is < 7.

Copy link
Member

@ViktorHofer ViktorHofer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The AssemblyVersion property in Versions.props must be hardcoded to 8.0.0.0 for now. We had the same issue last release and noticed that updating the TFM must happen in conjunction with reving the major assembly version.

Please also undo the changes in both CompatibilitySuppressions.xml, the TestData.resources one and the PACKAGE.md change which looks unrelated.

Prompted by the following getting caught as a warning, and converted to
an error:

```
EXEC : error : dotnet-install: Failed to check the disk space. Installation will continue, but it may fail if you do not have [D:\a\_work\1\s\src\mono\wasm\Wasm.Build.Tests\Wasm.Build.Tests.csproj]
   enough disk space.
  dotnet-install: Extracting the archive.
```
@radical
Copy link
Member

radical commented Aug 22, 2023

this script is being run with Exec msbuild task with IgnoreStandardErrorWarningFormat="true".

This was missing for the windows case!

@radical
Copy link
Member

radical commented Aug 22, 2023

/azp run runtime-wasm

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@jkoritzinsky
Copy link
Member

@radical if the WASM MT failures are known, can you merge this in?

@radical radical merged commit 96c2e1d into main Aug 23, 2023
192 of 195 checks passed
@radical radical deleted the BumpMainTo90Alpha1 branch August 23, 2023 00:15
@ghost ghost locked as resolved and limited conversation to collaborators Sep 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.