Skip to content
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

Disable CPM for OptProf tests #5598

Merged
merged 1 commit into from
Jan 16, 2024
Merged

Disable CPM for OptProf tests #5598

merged 1 commit into from
Jan 16, 2024

Conversation

zivkan
Copy link
Member

@zivkan zivkan commented Jan 15, 2024

Bug

Fixes: https://github.com/NuGet/Client.Engineering/issues/2656

Regression? yes Last working version: before #5572

Description

Explicitly disable CPM for OptProf test solution.

PR Checklist

  • PR has a meaningful title

  • PR has a linked issue.

  • Described changes

  • Tests

    • Automated tests added
    • OR
    • Test exception
    • OR
    • N/A
  • Documentation

    • Documentation PR or issue filled
    • OR
    • N/A

@zivkan zivkan requested a review from a team as a code owner January 15, 2024 22:01
@@ -1 +1,5 @@
<Project />
Copy link
Contributor

@kartheekp-ms kartheekp-ms Jan 16, 2024

Choose a reason for hiding this comment

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

May be the best option would have been to delete the Directory.Packages.props file completely because there are no properties defined in it.

Copy link
Member Author

Choose a reason for hiding this comment

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

If you run the test from VS, or dotnet test on the CLI, I'm worried it might find the repo root Directory.Packages.props. I assume that's why the file was added in the first place. There are also empty Directory.Build.props and targets files in the same directory.

@zivkan zivkan merged commit 9dd3357 into dev Jan 16, 2024
@zivkan zivkan deleted the dev-zivkan-fix-optprof branch January 16, 2024 23:17
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