8000 Poison leaks for NETStandard 2.1 and Microsoft.NET.Build.Extensions · Issue #5221 · dotnet/source-build · GitHub
[go: up one dir, main page]
Skip to content

Poison leaks for NETStandard 2.1 and Microsoft.NET.Build.Extensions #5221

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.

Sign up for GitHub

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

Jump to bottom
Closed
mthalman opened this issue May 28, 2025 · 2 comments · Fixed by dotnet/dotnet#847
Closed

Poison leaks for NETStandard 2.1 and Microsoft.NET.Build.Extensions #5221

mthalman opened this issue May 28, 2025 · 2 comments · Fixed by dotnet/dotnet#847
Assignees
@mthalman
Labels
ops-monitor Issues created/handled by the source build monitor role untriaged

Comments

@mthalman
Copy link
Member

Poison log: poison-usage.zip

Example build (internal link)

Seems to have been caused by either dotnet/dotnet#812 or dotnet/dotnet#798
@mthalman mthalman added the ops-monitor Issues created/handled by the source build monitor role label May 28, 2025
@MichaelSimons
Copy link
Member
MichaelSimons commented May 28, 2025 •
edited
Loading

Another piece to investigate is why the build is failing. The build should be creating a poison report and not failing the build. The poison test is what should actually fail the build. Quickly looking at the leaks, these appear to be what is in the baseline as allowed prebuilts.

@mthalman
Copy link
Member Author

Yep, the leak is matching the baseline so this is expected. It's failing the build because of dotnet/dotnet#798 which is now treating warnings as errors.

@mthalman mthalman mentioned this issue May 28, 2025
Merged
@MichaelSimons MichaelSimons moved this from Backlog to In Progress in .NET Source Build May 28, 2025
@github-project-automation github-project-automation bot moved this from In Progress to Done in .NET Source Build May 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mthalman mthalman

Labels
ops-monitor Issues created/handled by the source build monitor role untriaged
Projects
.NET Source Build
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Output poison leak as message instead of warning mthalman/dotnet
3 participants
@MichaelSimons @NikolaMilosavljevic @mthalman
0