-
Notifications
You must be signed in to change notification settings - Fork 446
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
Poison SBRP #17339
Poison SBRP #17339
Conversation
src/SourceBuild/content/repo-projects/source-build-reference-packages.proj
Outdated
Show resolved
Hide resolved
src/SourceBuild/content/repo-projects/source-build-reference-packages.proj
Outdated
Show resolved
Hide resolved
c77f382
to
22b41a2
Compare
...d/content/eng/tools/tasks/Microsoft.DotNet.SourceBuild.Tasks.LeakDetection/CheckForPoison.cs
Outdated
Show resolved
Hide resolved
...d/content/eng/tools/tasks/Microsoft.DotNet.SourceBuild.Tasks.LeakDetection/CheckForPoison.cs
Outdated
Show resolved
Hide resolved
...d/content/eng/tools/tasks/Microsoft.DotNet.SourceBuild.Tasks.LeakDetection/CheckForPoison.cs
Outdated
Show resolved
Hide resolved
...d/content/eng/tools/tasks/Microsoft.DotNet.SourceBuild.Tasks.LeakDetection/CheckForPoison.cs
Show resolved
Hide resolved
...d/content/eng/tools/tasks/Microsoft.DotNet.SourceBuild.Tasks.LeakDetection/CheckForPoison.cs
Outdated
Show resolved
Hide resolved
...Build/content/eng/tools/tasks/Microsoft.DotNet.SourceBuild.Tasks.LeakDetection/PoisonType.cs
Outdated
Show resolved
Hide resolved
ff0ea37
to
7e4372e
Compare
...d/content/eng/tools/tasks/Microsoft.DotNet.SourceBuild.Tasks.LeakDetection/CheckForPoison.cs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI the required SBRP changes flowing into installer in main is blocked as noted in #17310. It might be best to target release/8.0.
...Build/content/eng/tools/tasks/Microsoft.DotNet.SourceBuild.Tasks.LeakDetection/PoisonType.cs
Outdated
Show resolved
Hide resolved
One thing you may consider for testing purposes is to enable the poison check in the PR validation temporarily until you validate the changes. Then you can revert that change before you checkin. |
To clarify, I mean it might be best to have this PR target release/8.0 since the required SBRP changes have already flown into it and we want this in 8.0 anyways. |
3ce418a
to
5e596d9
Compare
…into poison-reference-assemblies
… value read, check sbrp display path
3ce418a
to
55ab6d5
Compare
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please update the poison baseline with this PR for the known leaks noted in dotnet/source-build#3670. If this is not done, it will fail the CI builds.
@MichaelSimons Yes! Updated in d1010d0 |
…into poison-ref-assemblies
Fixes dotnet/source-build#2817
These changes detect reference assembly leaks by checking for
System.Reflection.AssemblyMetadataAttribute("source", "source-build-reference-packages")
in built tarballs.