Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Jan 28, 2026

Description

Disables all tests under src/tests/tracing/userevents/ by setting CLRTestTargetUnsupported to true in the directory's Directory.Build.props.

Changes

Original prompt

Disable userevents tests by adding CLRTestTargetUnsupported to src/tests/tracing/userevents/Directory.Build.props with a link to #123442.


💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

Co-authored-by: mdh1418 <16830051+mdh1418@users.noreply.github.com>
Copilot AI changed the title [WIP] Disable userevents tests for CLRTestTargetUnsupported Disable userevents tests via CLRTestTargetUnsupported Jan 28, 2026
Copilot AI requested a review from mdh1418 January 28, 2026 21:33
@mdh1418 mdh1418 requested a review from noahfalk January 28, 2026 21:35
@mdh1418
Copy link
Member

mdh1418 commented Jan 28, 2026

The tests are flaking more than expected, disabling until more diagnostics like #123442 (comment) are added.

@mdh1418 mdh1418 requested a review from jkotas January 28, 2026 21:36
@mdh1418 mdh1418 marked this pull request as ready for review January 28, 2026 23:48
Copilot AI review requested due to automatic review settings January 28, 2026 23:48
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR disables all flaky userevents tests by setting CLRTestTargetUnsupported to true in their Directory.Build.props file. The tests are being disabled because they intermittently fail to capture expected .NET events in trace files, as documented in issue #123442.

Changes:

  • Added CLRTestTargetUnsupported property set to true in src/tests/tracing/userevents/Directory.Build.props
  • Added comment referencing the active issue #123442

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants