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.

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

Closed
1 of 2 tasks
epananth opened this issue Jun 16, 2021 · 12 comments
Closed
1 of 2 tasks

Publishing to symbol server is failing in runtime #7532

epananth opened this issue Jun 16, 2021 · 12 comments
Labels
Detected By - Customer Issue was reported by a customer Needs Triage A new issue that needs to be associated with an epic. Ops - First Responder

Comments

@epananth
Copy link
Member

epananth commented Jun 16, 2021

  • This issue is blocking
  • This issue is causing unreasonable pain

Publishing to symbol server we are experiencing some problem

image

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

@ghost ghost added the Needs Triage A new issue that needs to be associated with an epic. label Jun 16, 2021
@epananth
Copy link
Member Author

Note: Most recent change was

  1. Changed the symUploader build task from 1.1.152002 to 1.1.230702
  2. For out of memory issue we changed the number of maxclients from 20 to 16

@epananth epananth added Ops - First Responder Detected By - Customer Issue was reported by a customer labels Jun 16, 2021
@epananth
Copy link
Member Author

I am going to do a test with the older version of symuploader task to see if that will fix this..

@epananth
Copy link
Member Author

@epananth
Copy link
Member Author

@ViktorHofer
Copy link
Member

cc @hoyosjs @mangod9 @safern as we discussed this in the team's channel

@ViktorHofer
Copy link
Member

Note that this is blocking the snapped P6 bits from flowing. cc @Anipik @mmitche

@markwilkie
Copy link
Member

Are the more issues to deal with here beyond the symbolUploader version?

@mmitche
Copy link
Member

mmitche commented Jun 16, 2021

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.

@epananth
Copy link
Member Author

I don't think so either.. The one we saw in runtime was the only publishing failure we have seen after the change.

@hoyosjs
Copy link
Member

hoyosjs commented Jun 16, 2021

Sorry I didn't see this. Revert got handled in #7534 and we just discussed the fix.

@hoyosjs hoyosjs closed this as completed Jun 16, 2021
@ViktorHofer
Copy link
Member

In which issue are we tracking the fix for symuploader?

@hoyosjs
Copy link
Member

hoyosjs commented Jun 16, 2021

All source in that case is internal. We don't have a public facing issue or PR right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Detected By - Customer Issue was reported by a customer Needs Triage A new issue that needs to be associated with an epic. Ops - First Responder
Projects
None yet
Development

No branches or pull requests

5 participants