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

Fix wrong paths in SharedOutputPathAnalyzer. #10472

Merged
merged 4 commits into from
Aug 5, 2024
Merged

Conversation

AR-May
Copy link
Member

@AR-May AR-May commented Aug 1, 2024

Related to #10414

Context

PR #10238 added normalization of the path (which includes getting full path) before the project directory path is added to it. This led to the relative path being turned into a full path using CurrentDirectory instead of the project directory. This leads to enormous amount of false-positive analyzer's warnings (400 instead of 3) that cause the hang. This PR fixes the bug with paths and does not fix actual cause of a hang.

Changes Made

Reverted the PR #10238 and instead added normalization of the path later in the code when the project path is already combined with the relative path.

Testing

unit tests and local runs

@YuliiaKovalova
Copy link
Member

@AR-May , is it possible to cover it with some UTs to illustrate what problem got resolved?

@AR-May
Copy link
Member Author

AR-May commented Aug 2, 2024

@AR-May , is it possible to cover it with some UTs to illustrate what problem got resolved?

Added some extra test coverage. Test that illustrates this particular bug is TestTwoProjectsWithSameRelativeOutputPath.

Copy link
Member

@JanKrivanek JanKrivanek left a comment

Choose a reason for hiding this comment

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

Looks good - once the failing test is nailed down

@AR-May AR-May merged commit 7f6bc04 into dotnet:main Aug 5, 2024
10 checks passed
@AR-May AR-May self-assigned this Aug 5, 2024
@AR-May AR-May added the Priority:1 Work that is critical for the release, but we could probably ship without label Aug 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:1 Work that is critical for the release, but we could probably ship without
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants