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.
[release/2.1] Clean up `E_FAIL` compilation errors
See original GitHub issueThe SharedFx and later jobs emit loads (around 1000) of errors like:
Unspecified error (Exception from HRESULT: 0x80004005 (E_FAIL)) while compiling method MessagePackSerializer.SerializeAsync
These errors do not fail builds but do make for rather noisy logs❕ Would like to get to the bottom of this…
Problems are limited to the internal build pipeline and first show up around https://dev.azure.com/dnceng/internal/_build/results?buildId=997298. It’s not clear whether the problem existed before then because most builds were unsuccessful in the earlier “Build and test: Windows” job.
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
We have dotnet/coreclr#24386 fix in .NET Core 3.x branches, but not in 2.x ones. Considering .NET Core 2.1 is near its end-of-support, I am not sure whether there will be another release.
Errors are definitely annoying but we can wade through them forever more, just as we have been.