Skip to content

[cDAC] Change runtime-diagnostics pipeline trigger #117018

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 10 commits into
base: main
Choose a base branch
from

Conversation

max-charlamb
Copy link
Contributor

@max-charlamb max-charlamb commented Jun 25, 2025

Previously the runtime-diagnostics pipeline was not running on any PRs automatically due to an overridden ADO.

Modified ADO setting to let PR runs occur, but narrowing subset of files pipeline runs on to:

  • eng/pipelines/**
  • src/native/managed/cdac/**
  • src/coreclr/debug/runtimeinfo/** (where the datadescriptors are defined)

Copy link
Contributor

Tagging subscribers to this area: @steveisok, @dotnet/dotnet-diag
See info in area-owners.md if you want to be subscribed.

@steveisok
Copy link
Member

I had thought we wanted this to be manually triggered only?

@max-charlamb
Copy link
Contributor Author

It looks like @jkoritzinsky 's intent in #114718 was to have it trigger whenever cDAC files were modified in a PR. I think that behavior would be useful as well.

@max-charlamb max-charlamb marked this pull request as ready for review June 25, 2025 13:19
@Copilot Copilot AI review requested due to automatic review settings June 25, 2025 13:19
Copy link
Contributor

@Copilot 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 fixes the runtime-diagnostics pipeline trigger so that it runs automatically on PRs.
Key changes:

  • Updated the include patterns in the runtime-diagnostics YAML file.
  • Added a wildcard ("*") pattern to trigger the pipeline on all file changes.

@max-charlamb max-charlamb marked this pull request as draft June 25, 2025 13:34
@max-charlamb max-charlamb changed the title [cDAC] Fix runtime-diagnostics pipeline trigger [cDAC] Verify runtime-diagnostics pipeline trigger Jun 25, 2025
@max-charlamb max-charlamb changed the title [cDAC] Verify runtime-diagnostics pipeline trigger [cDAC] Change runtime-diagnostics pipeline trigger Jun 25, 2025
@max-charlamb max-charlamb marked this pull request as ready for review June 25, 2025 15:31
- '/src/coreclr/**'
- '/src/native/**'
- eng/pipelines/**
- src/native/managed/cdac/**
Copy link
Member

Choose a reason for hiding this comment

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

Would we not want this pipeline to run for PRs that are changing EventPipe logic /src/native/eventpipe?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm not sure. Currently this pipeline has mostly been used for testing the cDAC, but it is running all (?) of the diagnostic unit tests. If it would be useful or eventpipe I don't see why it shouldn't be added.

Do note, that this pipeline is not incorporated into build analysis and I don't think it will prevent merging.

Copy link
Member

Choose a reason for hiding this comment

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

From the intent of the PR that added this pipeline, it feels like we should include all paths that impact diagnostics. It does seem underutilized, probably because it needs to be manually triggered.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

If we don't mind the extra CI cost, it seems reasonable to have it on the existing subsets.

Copy link
Member

@mdh1418 mdh1418 Jun 25, 2025

Choose a reason for hiding this comment

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

If it is costly, we can keep it to your subsets for now, and expand it more when it makes sense.

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

Successfully merging this pull request may close these issues.

3 participants