It looks like there's an issue in .NET 5 preview1 where we set the main thread name and that somehow gets propagated as the process name on Linux (only) and so tests that check if it's pwsh ends up failing. I'll see about putting in some reasonable workarounds for now and add a pending test to verify the process name.

.NET 5 specifically has improvements to regex, so needed to increase the size of the DOS test

On Windows, pwsh is crashing in a native API call. Opened dotnet/runtime#33703

.NET 5 specifically has improvements to regex, so needed to increase the size of the DOS test

cc Stephen Toub (@stephentoub) 👏

It looks like there's an issue in .NET 5 preview1 where we set the main thread name and that somehow gets propagated as the process name on Linux (only)

Steve Lee (@SteveL-MSFT) is that a bug in .NET?

@danmosemsft The main thread name becoming the process name is a bug in .NET and is understood (dotnet/runtime#33673). That issue isn't blocking as it's currently only affecting tests and I made changes to work around it. The crashing issue (dotnet/runtime#33703) is preventing us from moving to .NET 5. Thanks!

There is already an issues filed for regex DOS tests: #12138

PoshChan-Bot (@PoshChan) retry macos

Steve Lee (@SteveL-MSFT), successfully started retry of PowerShell-CI-macOS

.NET originally said that the perf improvement was due to optimization, but it's actually due to a bug. I filed an issue to add it back to avoid delaying this PR.
#12155

.NET originally said that the perf improvement was due to optimization, but it's actually due to a bug

It's half and half :) The algorithmic complexity improved, in part due to perf improvements, and in part due to a bug fixed in Preview 2 (dotnet/runtime#33409).

🎉v7.1.0-preview.1 has been released which incorporates this pull request.:tada:

Handy links:

• Release Notes