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.

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

CI: Fuzzing-pipeline fails #155

Closed
gfoidl opened this issue Apr 13, 2020 · 3 comments · Fixed by #157
Closed

CI: Fuzzing-pipeline fails #155

gfoidl opened this issue Apr 13, 2020 · 3 comments · Fixed by #157
Assignees
@gfoidl
Labels
ci-pipeline fuzz

Comments

@gfoidl
Copy link
Owner

gfoidl commented Apr 13, 2020

CI for fuzz fails. Step init

CSC : error CS8032: An instance of analyzer gfoidl.Analyzers.PubternalityAnalyzer cannot be created from /home/vsts/.nuget/packages/gfoidl.analyzers/0.2.0/analyzers/netstandard2.0/gfoidl.Analyzers.dll : Could not load file or assembly 'Microsoft.CodeAnalysis, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. The system cannot find the file specified.. [/home/vsts/work/1/s/source/gfoidl.Base64/gfoidl.Base64.csproj]
@gfoidl gfoidl self-assigned this Apr 13, 2020
@gfoidl
Copy link
Owner Author

gfoidl commented Apr 14, 2020

With docker mcr.microsoft.com/dotnet/core/sdk tested. Can't repro with :5.0, but with :3.0. Interesting.

@gfoidl
Copy link
Owner Author

gfoidl commented Apr 14, 2020

Also with gfoidl.Analyzer v0.1.0 it builds.

@gfoidl
Copy link
Owner Author

gfoidl commented Apr 14, 2020

It seems to be an issue with NuGet, as it doesn't honor analyzer-assets as specified.
This issue shows up with .NET Core 3.0. Starting with .NET Core 3.1 this issue is gone.
.NET Core 3.0 has reached end of life, .NET Core 3.1 is a LTS release, so upgrading to .NET Core 3.1 should do the fix.

@gfoidl gfoidl mentioned this issue Apr 14, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gfoidl gfoidl

Labels
ci-pipeline fuzz
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Updated TFM for executables to .NET Core 3.1 gfoidl/Base64
1 participant
@gfoidl