Publishing to symbol server is failing in runtime

[epananth]

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

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

[epananth]

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]

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

[epananth]

reverting the symbolUploaderVersion seemed to have worked

https://dev.azure.com/dnceng/internal/_build/results?buildId=1189499&view=logs&j=ba23343f-f710-5af9-782d-5bd26b102304&t=ba23343f-f710-5af9-782d-5bd26b102304

[epananth]

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

[ViktorHofer]

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

[ViktorHofer]

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

[markwilkie]

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

[mmitche]

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]

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

[hoyosjs]

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