Update mac Helix queues

[agocke]

No description provided.

[ghost]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[safern]

Since we no longer have a diff between extra platforms for OSX_x64 I would recommend removing the OSX_64 legs that run libraries tests:

runtime/eng/pipelines/runtime-extra-platforms.yml

Line 87 in 09f681f

- OSX_x64

[agocke]

I'm not opposed, but I'd rather do it in a different PR, in case it causes unrelated problems.

[safern]

What worries me to delay it to a different PR is that usually those TODOs get delayed or slip on the backlog and we will just be wasting resources that are useful on the extra-platforms run.

[safern]

Or at least if it is a subsequent PR you'll do in the next day or so, I don't mind.

[agocke]

@elinor-fung@AaronRobinsonMSFT@jkoritzinsky would you mind looking at this PR? After I upgraded the tests to use the latest Mac machines, it looks like some DllImport unit tests are failing

[elinor-fung]

It looks like that test case is relying on setting LD_LIBRARY_PATH.

runtime/src/tests/Interop/DllImportAttribute/DllImportPath/DllImportPathTest.csproj

Line 11 in daf77fc

<CLRTestBashEnvironmentVariableInclude="export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$%28pwd)/Subdirectory" />

Maybe this is that macOS security thing where they purge LD_LIBRARY_PATH (and DYLD_LIBRARY_PATH) when starting child processes? If it is that, I'd be fine just not running the TestNativeLibraryProbingOnPathEnv case on macOS:

runtime/src/tests/Interop/DllImportAttribute/DllImportPath/DllImportPathTest.cs

Line 181 in 57bfe47

TestNativeLibraryProbingOnPathEnv();

[agocke]

Sounds good, I'll skip the test.

[steveisok]

Is the OSX failure related? If not, is this ready to go?

[akoeplinger]

Only the OSX.1014.Amd64 queue was removed so we could keep the 10.15 ones.

[premun]

FYI there is this overview - https://github.com/dotnet/core-eng/wiki/Mobile-devices-for-.NET-testing (there are almost all OSX queues listed there, not just mobile)

The 12.00 is the largest queue by far with zero load, so we should definitely move some of the 10.14 workloads there (if possible). 10.15 is the most stressed queue at the moment if I am not mistaken.

[premun]

Btw we have a related discussion ongoing - do we need docker on OSX queues?

[agocke]

@tommcdon It looks like a few profiler tests are failing on the new MacOS version. Could someone on your team take a look?

[safern]

@agocke can we disable the test and open an issue in order to unblock other PRs?

[agocke]

@safern Yes, I didn't realize other PRs were failing. I'll do this immediately.

[agocke]

This is failing every PR so I don't think it can get worse. I'm going to merge now.