Skip to content

Conversation

@jakobbotsch
Copy link
Member

@jakobbotsch jakobbotsch commented May 18, 2022

As discussed in #67728, move this to a newer OS. windowsservercore-2004 has been EOL since Dec 2021.

If I understand correctly windowsservercore-ltsc2019 should be the oldest server OS that we still support
apart from 20H2 which is EOL in a couple of months, so I suggest we skip that one.

Fixes #67728

…dowsservercore-ltsc2019

This should be the oldest server OS that we still support apart from
20H2 which is EOL in a couple of months.
@ghost
Copy link

ghost commented May 18, 2022

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

Issue Details

If I understand correctly this should be the oldest server OS that we still support
apart from 20H2 which is EOL in a couple of months, so I suggest we skip that one.

Author: jakobbotsch
Assignees: jakobbotsch
Labels:

area-Infrastructure-libraries

Milestone: -

@jakobbotsch
Copy link
Member Author

/azp run runtime-extra-platforms, runtime-libraries-coreclr outerloop-windows

@azure-pipelines
Copy link

Azure Pipelines successfully started running 2 pipeline(s).

@jakobbotsch jakobbotsch changed the title Switch extra coverage in outerloop from windowsservercore-2004 to windowsservercore-ltsc2019 Switch extra platform coverage from windowsservercore-2004 to windowsservercore-ltsc2019 May 18, 2022
@jakobbotsch
Copy link
Member Author

jakobbotsch commented May 18, 2022

@dotnet/area-system-io A couple of System.IO.Ports tests are failing on the Windows Server 2019 OS added in this PR (see the net7.0-windows-Release-x64-CoreCLR_release-(Windows.10.Amd64.ServerRS5.Open)... tests).

These tests are already disabled on Nano Server, but it looks to me that the tests should be expected to succeed. AllGetPortNamesAreInHelperPorts prints the following:

COM1 is not present in PortHelper.GetPorts result
PortHelper Ports:
SerialPort Ports: COM1,COM2

Expected: True
Actual:   False

OpenEveryPortName prints the following:

System.IO.FileNotFoundException : Could not find file 'COM1'.

This implies to me that SerialPort.GetPortNames() is not working correctly on Windows Server 2019 OS (and presumably on Nano Server if the tests weren't disabled there). Thoughts? Is the failure expected or not?

I will disable the tests on Windows Server Core as well to unblock this, but not sure if it's the right long term solution.

@jakobbotsch
Copy link
Member Author

/azp run runtime-extra-platforms, runtime-libraries-coreclr outerloop-windows

@azure-pipelines
Copy link

Azure Pipelines successfully started running 2 pipeline(s).

@jakobbotsch jakobbotsch marked this pull request as ready for review May 18, 2022 16:15
@jakobbotsch
Copy link
Member Author

Failures are #69493, #69406 and Mono jobs that this PR does not affect.

@jakobbotsch jakobbotsch requested a review from a team May 18, 2022 16:19
@ViktorHofer
Copy link
Member

ping @dotnet/area-system-io for @jakobbotsch question above.

cc @danmoseley as you experimented in the past with windows server core

@jakobbotsch
Copy link
Member Author

@leecow @richlander @danmoseley @agocke Can you help provide guidance on what Server Core OS we should be testing here?

Previously we were testing Server Core 2004 which according to this page has been EOL since December last year. This PR is updating the coverage to Server Core LTSC2019 that is supported until 2024.
However, there are clearly other alternatives listed on that page, e.g. Server Core 2016 has extended support until 2027. So now @ViktorHofer and I are unsure what we should actually be testing here.

@jozkee
Copy link
Member

jozkee commented May 20, 2022

A couple of System.IO.Ports tests are failing

@jakobbotsch was the failure consistent? it may be flakyness in the Ports test, did you hit retry? in any case, the best is to file an issue to address the error.

/// </summary>
[ConditionalFact(typeof(PlatformDetection), nameof(PlatformDetection.IsNotWindowsNanoServer))]
[ConditionalFact(typeof(PlatformDetection), nameof(PlatformDetection.IsNotWindowsNanoNorServerCore))]
[ActiveIssue("https://github.com/dotnet/runtime/issues/34490", TestPlatforms.Windows, TargetFrameworkMonikers.Netcoreapp, TestRuntimes.Mono)]
Copy link
Member

Choose a reason for hiding this comment

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

This issue is closed.

Suggested change
[ActiveIssue("https://github.com/dotnet/runtime/issues/34490", TestPlatforms.Windows, TargetFrameworkMonikers.Netcoreapp, TestRuntimes.Mono)]

Copy link
Member Author

Choose a reason for hiding this comment

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

I think you should submit a separate PR to see if this can be reenabled on Mono. This PR is not about System.IO.Ports so I would rather not change this and end up with two more rounds of CI in case this is still blocked on something.

@jakobbotsch was the failure consistent? it may be flakyness in the Ports test, did you hit retry? in any case, the best is to file an issue to address the error.

I did not retry. I doubt this is just flakyness given the two separate failing tests and their log output (File.Open failed for COM1 and PortHelper.GetPorts seems to correctly report the available ports, while SerialPort.PortNames does not).

@richlander
Copy link
Member

Looks like you are on the right path.

FYI: LTSC 2019 is the primary OS for Windows containers in AKS.

@jakobbotsch
Copy link
Member Author

I'll give a bit more time for feedback and otherwise merge this at the end of the day.

Copy link
Member

@agocke agocke left a comment

Choose a reason for hiding this comment

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

LGTM, although I wonder if we should define these as variables so we don't have to edit in multiple places

@jakobbotsch jakobbotsch merged commit a093b34 into dotnet:main May 25, 2022
@jakobbotsch jakobbotsch deleted the roll-forward-server-queues branch May 25, 2022 14:49
@ghost ghost locked as resolved and limited conversation to collaborators Jun 24, 2022
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.

runtime-extra-platforms rolling build failure: Docker Internal Server Error - The container operating system does not match the host operating system.

5 participants