b1ea4b51aa
This allows the CI to run ALL the tests that the project has in parallel. This is divided in two main changes: 1. Xharness - We move away from using boolenas to use a flag that states the tests to run. 2. yaml - We have move the code to use a template per label. This new jobs all run in parallel and the results are later collected by a funel job 3. pwsh - Added a new class that understands that we have several mark downs with the tests results. The classes parses them and them writes a single comment (and example can be found here: https://github.com/xamarin/xamarin-macios/pull/15201#issuecomment-1162366240 The changes gives the following advantages vs how we used to run tests: 1. The CI run for all tests moves from taking 13 hours to 3/4 hours (depending on the number of bots in the pool). 2. The download needed to verify the results on a case of failure is smaller. Rather than downloading several GBs we now just download that part of the html that we are interested in. 3. Better bot utlization. Bots are just used to a max of 2 hours, this means that we can use the bots better since they are fragmented. 4. Less VMs. VSDrops has added support for macOS and Linux, we take advanges of that here. Co-authored-by: Rolf Bjarne Kvinge <rolf@xamarin.com> |
||
|---|---|---|
| .. | ||
| AttributeTest.cs | ||
| CecilExtensions.cs | ||
| ConstructorTest.cs | ||
| EnumTest.cs | ||
| Helper.cs | ||
| Makefile | ||
| MarshalAsTest.cs | ||
| ObsoleteTest.cs | ||
| OpenTKTest.cs | ||
| README.md | ||
| Test.cs | ||
| cecil-tests.csproj | ||
| cecil-tests.sln | ||
README.md
Cecil-based Tests
Even with the huge variety of tests that we have there's still a few things that are hard to test properly. Some of them can be tested by analyzing the assemblies (IL or metadata). So here we are...