Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[BUG]Intermittent Failure in .Net CI
See original GitHub issueDescribe the bug
CI sometimes fails with
error : Failed to resolve SDK 'Microsoft.Build.CentralPackageVersions/2.0.36'. Package restore was successful but a package with the ID of "Microsoft.Build.CentralPackageVersions" was not installed.
To Reproduce Steps to reproduce the behavior: Queue a PR build
Expected behavior Pipeline fails at random
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:11 (8 by maintainers)
Top Results From Across the Web
[BUG] Intermittent 'Authentication failed: Response was not ...
Library name and version Azure.ResourceManager 1.3.1 Describe the bug We are observing an 'Authentication failed: Response was not set, ...
Read more >c# - What could cause intermittent build failures in teamcity ...
I am maintaining a build configuration in Teamcity. It works most of the time, but about 1/8 of the time it fails with...
Read more >Troubleshoot pipeline runs - Azure DevOps
Intermittent or inconsistent errors may indicate that your target configuration is incompatible with the concurrent-process feature of MSBuild. ...
Read more >How to Fix Flaky Tests - Semaphore CI
A test that intermittently fails for no apparent reason — or works in your local machine and fails with continuous integration — is...
Read more >dotnet restore fails when fetching from telerik servers
I've got the same problem - intermittent failures with a 500 internal server error. It generally takes us 1-2 times restarting the workflow...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m fixing this issue in https://github.com/Azure/azure-sdk-for-net/pull/7705 by eliminating the nuget resolver from our usage and directly checking in the props/targets file from the central package version nupkg. If the nuget resolver issue gets fixed we can later consider using the sdk import again.
The workaround did not solve the problem. The bug still exists as it occurred yesterday here