Help with RazorExtension.dll failing SymbolCheck
See original GitHub issueBuild
Razor insertions are failing SymbolCheck for one specific DLL, and I’ve tried to dig in to find out why, but I have reached my limit, and would appreciate some guidance or assistance.
eg, on our most recent insertion: https://devdiv.visualstudio.com/DevDiv/_git/VS/pullrequest/420798
SymbolCheck failed for microsoft.visualstudio.razorextension.dll https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=6631089&view=logs&j=fd490c07-0b22-5182-fac9-6d67fe1e939b&t=da4239c9-cabf-50a7-e7ce-52be5c6d9883&s=96ac2280-8cb4-5df5-99de-dd2da759617d (Make sure you look at Attempt 1 in the build log. I tried to re-run the build out of curiosity, but it failed because the PR had already been merged and branch gone)
SymbolCheck issue: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1601388/
Build leg reported
SymbolCheck
Pull Request
https://devdiv.visualstudio.com/DevDiv/_git/VS/pullrequest/420798
Action required for the engineering services team
To triage this issue (First Responder / @dotnet/dnceng):
- Open the failing build above and investigate
- Add a comment explaining your findings
If this is an issue that is causing build breaks across multiple builds and would get benefit from being listed on the build analysis check, follow the next steps:
- Add the label “Known Build Error”
- Edit this issue and add an error string in the Json below that can help us match this issue with future build breaks. You should use the known issues documentation
{
"ErrorMessage" : "There are 1 unarchived files",
"BuildRetry": false
}
Additional information about the issue reported
I’m not even sure where to look for logs/artifacts for the symbol publishing part of our CI build so even that information could be useful, but if you want to go all the way and open a PR, I’ll accept that too 😄
Report
Summary
24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
---|---|---|
0 | 0 | 0 |
Issue Analytics
- State:
- Created a year ago
- Comments:11 (9 by maintainers)
Top GitHub Comments
Thanks for the detailed info @hoyosjs, in particular “you call build twice” helped me work out where to look 😃
@hoyosjs do you have a few minutes to help out?