Closed ericstj closed 5 months ago
Oddly enough, I just checked and the latest build out of main
is available. I also double checked a build out of main
from 2 BS 3 months ago and they also available. Odd that only this release build is missing. (note all are still missing native symbols)
So it's only the release build. The release build was also never actually published to our feeds. So perhaps symbol publishing is part of the pipeline that's "delayed" in a stable release build. Maybe we need to kick off the actual publishing of that build to get it's symbols published.
Ok, so with the latest arcade changes to switch to .symbols.nupkg native symbols publishing is now working correctly.
The only remaining gap here is why we don't get publishing for release builds. I believe that's because the builds don't get promoted to any channel by darc publish. I think we can fix this by adding a step to our release process to manually promote the build with a darc command (once we decide which build we want to publish). I'm waiting for confirmation on this.
We discovered the problem with the release builds. It had to do with our darc channel configuration for release braches. That's been fixed now.
Last piece here is to port the changes to release.
Fixed in 3.0.1
Describe the bug Using the latest Microsoft.ML packages, I can't resolve symbols.
To Reproduce
Output with public server:
Output with internal server:
Sample verbose output for a single assembly:
Expected behavior All ML assembly's symbols are published to both internal and public symbol servers.
I suspect at some point our symbol publishing broke. I spot checked 2.0.1 and it was working, but only for managed assemblies. Modifying the above sample to use 2.0.1 instead of 3.0.0 I get:
Going back we had this same problem with native binaries in previous releases as well. We should make sure we fix that as part of this.