[tvOS] Test failures in System.Diagnostics.Tracing.Tests

[MaximLipnin]

• BasicEventSourceTests.ActivityTracking.StartStopCreatesActivity

  <failure exception-type="Xunit.Sdk.NotEqualException">
  <message><![CDATA[Assert.NotEqual() Failure\nExpected: Not 00000000-0000-0000-0000-000000000000\nActual:   00000000-0000-0000-0000-000000000000]]></message>
  <stack-trace><![CDATA[   at BasicEventSourceTests.ActivityTracking.StartStopCreatesActivity()
  at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)]]>
  </stack-trace>
  </failure>

• BasicEventSourceTests.ActivityTracking.ActivityFlowsAsync

  <failure exception-type="Xunit.Sdk.NotEqualException">
  <message><![CDATA[Assert.NotEqual() Failure\nExpected: Not 00000000-0000-0000-0000-000000000000\nActual:   00000000-0000-0000-0000-000000000000]]></message>
  <stack-trace><![CDATA[   at BasicEventSourceTests.ActivityTracking.ActivityFlowsAsync()
  --- End of stack trace from previous location ---]]>
  </stack-trace>
  </failure>

• BasicEventSourceTests.ActivityTracking.SetCurrentActivityIdBeforeEventFlowsAsync

  <failure exception-type="Xunit.Sdk.EqualException">
  <message><![CDATA[Assert.Equal() Failure\nExpected: ed27419e-317a-43a7-be88-6b793b146141\nActual:   00000000-0000-0000-0000-000000000000]]></message>
  <stack-trace><![CDATA[   at BasicEventSourceTests.ActivityTracking.SetCurrentActivityIdBeforeEventFlowsAsync()
  --- End of stack trace from previous location ---]]>
  </stack-trace>
  </failure>

• BasicEventSourceTests.ActivityTracking.SetCurrentActivityIdAfterEventDoesNotFlowAsync

  <failure exception-type="Xunit.Sdk.EqualException">
  <message><![CDATA[Assert.Equal() Failure\nExpected: 33f1669b-7f05-46a8-bf4c-f321de6083f6\nActual:   00000000-0000-0000-0000-000000000000]]></message>
  <stack-trace><![CDATA[   at BasicEventSourceTests.ActivityTracking.SetCurrentActivityIdAfterEventDoesNotFlowAsync()
  --- End of stack trace from previous location ---]]>
  </stack-trace>
  </failure>

cc @steveisok

[dotnet-issue-labeler[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.

[MaximLipnin]

Those tests have been added recently in https://github.com/dotnet/runtime/pull/55625. They are skipped for WASM, I'm not sure if we want to do the same for Apple mobile platforms.

[ghost]

Tagging subscribers to this area: @tarekgh, @tommcdon, @pjanotti See info in area-owners.md if you want to be subscribed.

Issue Details

---

- BasicEventSourceTests.ActivityTracking.StartStopCreatesActivity ``` ``` - BasicEventSourceTests.ActivityTracking.ActivityFlowsAsync ``` ``` - BasicEventSourceTests.ActivityTracking.SetCurrentActivityIdBeforeEventFlowsAsync ``` ``` - BasicEventSourceTests.ActivityTracking.SetCurrentActivityIdAfterEventDoesNotFlowAsync ``` ``` cc @steveisok

Author:	MaximLipnin
Assignees:	-
Labels:	`area-System.Diagnostics.Tracing`, `untriaged`
Milestone:	-

[steveisok]

@MaximLipnin Can you check to see what the value is for <EventSourceSupport> ?

[MaximLipnin]

@steveisok Something close to the mobile targets is https://github.com/dotnet/runtime/blob/main/eng/testing/tests.mobile.targets#L26 but we don't set EAT for the staging lanes so perhaps EventSourceSupport is not set

[lateralusX]

Do we build with diagnostics tracing component support enabled when running tests on mobile, link or deploy needed components? I guess this tests will end up in ves_icall_System_Diagnostics_Tracing_EventPipeInternal_EventActivityIdControl and if we don't have component support loaded that will be a nop operation so won't set thread activity ID and that will trigger the assert in this test.

[steveisok]

I don't think we do. We probably should skip these for the time being.

[ghost]

Tagging subscribers to 'arch-android': @steveisok, @akoeplinger See info in area-owners.md if you want to be subscribed.

Issue Details

---

- BasicEventSourceTests.ActivityTracking.StartStopCreatesActivity ``` ``` - BasicEventSourceTests.ActivityTracking.ActivityFlowsAsync ``` ``` - BasicEventSourceTests.ActivityTracking.SetCurrentActivityIdBeforeEventFlowsAsync ``` ``` - BasicEventSourceTests.ActivityTracking.SetCurrentActivityIdAfterEventDoesNotFlowAsync ``` ``` cc @steveisok

Author:	MaximLipnin
Assignees:	-
Labels:	`area-System.Diagnostics.Tracing`, `os-android`, `os-ios`
Milestone:	-

[ghost]

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

Issue Details

---

- BasicEventSourceTests.ActivityTracking.StartStopCreatesActivity ``` ``` - BasicEventSourceTests.ActivityTracking.ActivityFlowsAsync ``` ``` - BasicEventSourceTests.ActivityTracking.SetCurrentActivityIdBeforeEventFlowsAsync ``` ``` - BasicEventSourceTests.ActivityTracking.SetCurrentActivityIdAfterEventDoesNotFlowAsync ``` ``` cc @steveisok

Author:	MaximLipnin
Assignees:	-
Labels:	`area-Infrastructure-mono`, `area-System.Diagnostics.Tracing`, `os-android`, `os-ios`
Milestone:	-

[steveisok]

These are now enabled. Closing.

[mdh1418]

These are still failing on tvOS