runtime-community leg failing for ThreadPoolMinMaxThreadsEventTest

[tannergooding]

This has been failing since #70063 (https://dev.azure.com/dnceng/public/_build/results?buildId=1831349&view=ms.vss-test-web.build-test-results-tab).

CC. @eduardo-vp

[dotnet-issue-labeler]

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.

[tannergooding]

Notably the community leg is for linux release s390x mono. It represents a big endian platform.

[uweigand]

Thanks for reporting this!

Looking at the failing test, we have this failed assertion:

          Child exception:
            Xunit.Sdk.EqualException: Assert.Equal() Failure
          Expected: 3
          Actual:   768
          /home/uweigand/runtime/src/libraries/System.Threading.ThreadPool/tests/ThreadPoolTests.cs(1147,0): at System.Threading.ThreadPools.Tests.ThreadPoolTests.<>c.<ThreadPoolMinMaxThreadsEventTest>b__42_0()

Note that 768 is 0x300 and this value is of type uint16_t, so it looks like a missed endian conversion.

I think this is related to the general endian problems with eventpipe that @stefan-sf has been working on for a while, see in particular #68648. @stefan-sf can you confirm that that PR would fix this new issue as well?

[ghost]

Tagging subscribers to this area: @mangod9
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This has been failing since #70063 (https://dev.azure.com/dnceng/public/_build/results?buildId=1831349&view=ms.vss-test-web.build-test-results-tab).

CC. @eduardo-vp

Author:	tannergooding
Assignees:	-
Labels:	area-System.Threading, untriaged
Milestone:	-

[stefan-sf-ibm]

Did a rebase today and can confirm that ThreadPoolMinMaxThreadsEventTest passes if #68648 is applied.

[uweigand]

Thanks, @stefan-sf-ibm !

[mangod9]

so this issue can be closed I assume?

[uweigand]

Yes, our CI is now green again. This issue can be closed.

[mangod9]

Thx!