Libraries trimming test are missing a lot of configurations

[marek-safar]

Newly added trimming libraries tests run only for configurations which are not by default trimmed aggressively. All the ones which are and are used to customers are missing so we have no test coverage.

Mandatory RIDs to be added to the existing matrix

• browser-wasm
• ios-arm64
• tvos-arm64
• android-arm64

[Dotnet-GitSync-Bot]

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

Tagging subscribers to this area: @safern, @ViktorHofer
Notify danmosemsft if you want to be subscribed.

[safern]

Cc: @joperezr

[joperezr]

Although we do plan to enable a few extra platforms, with the trimming tests we are manually changing the way we invoke the linker in order to force aggressive trimming so we do have coverage for now. That said, I do want to restate that we do plan to add at least wasm platform as well

[safern]

@joperezr could you add the right milestone on when you're going to be adding these? At least browser seems important for 5.0.0

[joperezr]

yup, wasm will be done before 5.0 definitely.

[ViktorHofer]

@joperezr it's unclear to me what the remaining work is. Is someone actively working on this? Thanks

[joperezr]

We still haven't added a wasm leg for the linker tests, today we only have these 3:

runtime/eng/pipelines/runtime-linker-tests.yml

Lines 61 to 64 in afa4b2f

	platforms:
	- Windows_NT_x64
	- OSX_x64
	- Linux_x64

Ideally we would want to add wasm in there as well to build that vertical and run linker tests for that runtime, so that would be the remaining work. @eerhardt do we still want to do that for 5.0?