63de01c21c
I recently deleted the generated makefile support for building and running our test suites. It turned out that it was used for building the packaged Xamarin.Mac tests, so it wasn't as unused as I thought. So fix the building and packaging of Xamarin.Mac tests to not use the (non-existent) makefile targets, but instead replicate it with manual make code. Also take the opportunity to add packaging and execution of the .NET versions of these test suites we execute on other macOS versions (both for macOS and the Mac Catalyst). * [devops] Use stricter matching when finding the Xamarin.Mac pkg link. Otherwise the branch name in any package could end up matching the pattern we were looking for: XM_PACKAGE=https://bosstoragemirror.blob.core.windows.net/wrench/tests-package-xamarin-mac-tests/15759261d425ae08494b0a26862a0b1356c5f8ec/5268864/package/Microsoft.iOS.Bundle.15.0.101-ci.tests-package-xamarin-mac-tests.68.pkg is just clearly wrong. |
||
|---|---|---|
| .. | ||
| dont link | ||
| link all | ||
| link sdk | ||
| README.md | ||
README.md
Linker Regression Tests
Most of our unit tests follow the default project configuration, which is "Don't Link" for simulator builds and "Link SDK" for device builds.
The linker tests are different as they set both simulator and device configuration to the same settings. This is the main way to test the linker on the simulator (which is the most common test configuration for our bots)
Note that the spaces in the projects directory names are by design as it ensure our tool chain can cope with them.
dont link
-
regression testing without using the linker
-
both simulator and devices are set to "Don't link"
link all
-
regression testing using the linker on the all assemblies
-
"Link all assemblies" for both simulator/devices
link sdk
-
regression testing using the linker on the SDK assemblies
-
"Link SDK assemblies only" for both simulator/devices