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 that CI builds sometimes produce different analyzer violations than local builds (OSOE-855) #99

Closed
Piedone opened this issue May 15, 2024 · 3 comments · Fixed by Lombiq/GitHub-Actions#361
Assignees
Labels
bug Something isn't working

Comments

@Piedone
Copy link
Member

Piedone commented May 15, 2024

See e.g. this most recent example: Lombiq/Helpful-Libraries#261. I also started an investigation there.

Jira issue

@Piedone Piedone added the bug Something isn't working label May 15, 2024
@github-actions github-actions bot changed the title Fix that CI builds sometimes produce different analyzer violations than local builds Fix that CI builds sometimes produce different analyzer violations than local builds (OSOE-855) May 15, 2024
@Piedone Piedone self-assigned this May 15, 2024
@Piedone
Copy link
Member Author

Piedone commented May 15, 2024

My minimal repro still surfaces the issue under .NET v8.0.204: https://github.com/Lombiq/OSOE-855-AnalyzersTest/actions/runs/9096693522/job/25002706433

@Piedone
Copy link
Member Author

Piedone commented Jun 5, 2024

We need to pin the .NET version number: dotnet/roslyn#73639 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
1 participant