-
Notifications
You must be signed in to change notification settings - Fork 10.4k
[release/7.0] Move to an RTM SDK #44233
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess 7.0.100-rtm.22477.16
is from the internal branch, 7.0.100-rtm.22478.12
is the latest I could find from a build of release/7.0.1xx
It's the version https://aka.ms/dotnet/7.0.1xx/daily/productCommit-win-x64.txt shows. I asked @marcpopMSFT in FR whether we should prefer that or the version from https://github.com/dotnet/installer. Also asking FR people how previous problems like this have been resolved. |
That looks like a bug in the table, here's the build that produced it (note it's of internal/release/7.0.1xx): https://dev.azure.com/dnceng/internal/_build/results?buildId=2005514&view=results |
https://aka.ms/dotnet/7.0.1xx/daily/productCommit-win-x64.txt better not refer to internal builds because that's a public file |
Think I figured it out. I took the version from the SDK line in productCommit-win-x64.txt instead of the installer line. Note we normally build and make daily builds public from the internal/… branches. It's only internal & secure builds that won't touch the As far as I can see, nothing is wrong w/ either dotnet/installer or the productCommit-win-x64.txt file. @marcpopMSFT you can stand down 😁 |
The internal/* branches are never public. Only the release/* branches are. |
Most template tests failing w/ Failure to uninstall
Failure to install
I'll check for differences in the relevant files between release/7.0 and main. |
Will retry after #44246 is in; that may help here. |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
- `cherry-pick`ed from d184b97
92d2071
to
a5793ba
Compare
@wtgodbe and @BrennanConroy thanks very much for your help w/ this❕ |
No description provided.