-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Propogate repair commands to inner bundles in Hosting Bundle #33588
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
joeloff
left a comment
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.
Awesome, thanks for the quick turn around
|
/backport to release/5.0 |
|
/backport to release/3.1 |
|
/backport to release/2.1 |
|
Started backporting to release/5.0: https://github.com/dotnet/aspnetcore/actions/runs/947134773 |
|
Started backporting to release/3.1: https://github.com/dotnet/aspnetcore/actions/runs/947134957 |
|
Started backporting to release/2.1: https://github.com/dotnet/aspnetcore/actions/runs/947135135 |
Clean machine is best, just to make it easier to find the logs. Install the hosting bundle, then from a commandline, run the bundle with In the repair log of the hosting bundle you should see it invoking the dotnet runtime bundles with /repair. But if it did, you should also see setup logs from the runtime bundle appearing in %temp%. |
Should fix #33572
@joeloff how can I test this once I have a build?