-
Notifications
You must be signed in to change notification settings - Fork 342
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
Publishing to symbol server is failing in runtime #7532
Comments
Note: Most recent change was
|
I am going to do a test with the older version of symuploader task to see if that will fix this.. |
reverting the symbolUploaderVersion seemed to have worked |
tried another failed runtime build https://dev.azure.com/dnceng/internal/_build/results?buildId=1189556&view=logs&j=ba23343f-f710-5af9-782d-5bd26b102304&t=ba23343f-f710-5af9-782d-5bd26b102304, seems like something with the SymUploader version |
Are the more issues to deal with here beyond the symbolUploader version? |
I don't think so? Let's get the version reverted. FYI I'm promoting the latest main and p6 runtime builds using epsi's branhc. |
I don't think so either.. The one we saw in runtime was the only publishing failure we have seen after the change. |
Sorry I didn't see this. Revert got handled in #7534 and we just discussed the fix. |
In which issue are we tracking the fix for symuploader? |
All source in that case is internal. We don't have a public facing issue or PR right now. |
Publishing to symbol server we are experiencing some problem
So I did a check if the symbol actually got uploaded
https://microsoft.artifacts.visualstudio.com/defaultcollection/_apis/symbol/symsrv/mscordaccore.dll/60C90EE5870000/mscordaccore.dll
Looks like it somewhere in the middle we encounter that the stream is disposed
The text was updated successfully, but these errors were encountered: