-
Notifications
You must be signed in to change notification settings - Fork 4.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
Update RedHat 7 -> 8 -- release/6.0-staging #105063
Update RedHat 7 -> 8 -- release/6.0-staging #105063
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.
I don't know the format of these files too well, but the general change from 7 to 8 makes sense to me.
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
No equivalent PR for |
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.
@richlander this is failing:
.packages/microsoft.dotnet.helix.sdk/6.0.0-beta.24360.7/tools/Microsoft.DotNet.Helix.Sdk.MonoQueue.targets(59,5): error : (NETCORE_ENGINEERING_TELEMETRY=Build) Helix API does not contain an entry for RedHat.8.Amd64.Open
Approving for servicing as tell-mode. You can merge anytime if the CI looks good. |
Silly me. I didn't realize that we didn't have a RHEL 8 queue. Tracking issue: dotnet/dnceng#3867. I also didn't realize that they list was available: https://helix.dot.net/ |
@richlander any updates on this? Is it ready to merge? |
Thanks for checking in. The tracking issue is still open. |
BTW friendly reminder: Code Complete for the October Release is September 9. If we want this fix to be included in that release, please merge this PR before that date. Otherwise, it will have to wait until November. |
Removing |
@richlander we are going to need this PR merged soon as all existing PRs in the release/6.0-staging are now failing with the following error:
Examples: https://github.com/dotnet/runtime/pull/108300/checks?check_run_id=30735541280 , https://github.com/dotnet/runtime/pull/107828/checks?check_run_id=30735326967 , https://github.com/dotnet/runtime/pull/107826/checks?check_run_id=30735395206 , https://github.com/dotnet/runtime/pull/107764/checks?check_run_id=30735049259 |
I'll raise this with the right folks. |
My thinking is:
|
/ba-g The wasm "connection refused" and "Chrome was unable to start" failures that did not get linked to an issue are unrelated to this PR. One of them is #104349 |
8b6500b
into
dotnet:release/6.0-staging
- dotnet/dnceng#4298 part 1/II - contributes to dotnet/dnceng#3189 - use Docker container for CentOS, mimicking dotnet/runtime#105063
- dotnet/dnceng#4298 part II/II - contributes to dotnet/dnceng#3189 - use Docker container for CentOS, mimicking dotnet/runtime#105063
- dotnet/dnceng#4298 part II/II - contributes to dotnet/dnceng#3189 - use Docker container for CentOS, mimicking dotnet/runtime#105063
- dotnet/dnceng#4298 part I/II - contributes to dotnet/dnceng#3189 - use Docker container for CentOS, mimicking dotnet/runtime#105063
- dotnet/dnceng#4298 part II/II - contributes to dotnet/dnceng#3189 - use Docker container for CentOS, mimicking dotnet/runtime#105063
Red Hat no longer supports .NET 6 on RHEL 7.
Context: https://access.redhat.com/support/policy/updates/net-core
Also resolving #103380 (comment)
@omajid @akoeplinger