-
Notifications
You must be signed in to change notification settings - Fork 445
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
[release/5.0.1xx-preview5] Update dependencies from dotnet/runtime #7490
[release/5.0.1xx-preview5] Update dependencies from dotnet/runtime #7490
Conversation
…0513.12 Microsoft.NETCore.App.Runtime.win-x64 , Microsoft.NETCore.DotNetHostResolver , Microsoft.NETCore.Platforms , Microsoft.NETCore.App.Host.win-x64 , Microsoft.NETCore.App.Internal , Microsoft.NETCore.App.Ref From Version 5.0.0-preview.6.20264.1 -> To Version 5.0.0-preview.5.20263.12
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
/azp run |
Commenter does not have sufficient privileges for PR 7490 in repo dotnet/installer |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@sfoslund @dsplaisted @wli3 Can you take a look here? |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
This reminds me of the failure from #7005 |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
Okay should verify that all that was in p4 got into p5 for runtime. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
What reminds you that issue? The exit code in the log is different - it is 150. If it is an error code stemming from a signal, then the signal causing the crash would be SIGTTOU, which would mean that a background process attempted to write to console. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@janvorli my bad, I missed that. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@janvorli could you help me find someone from runtime team to lead the investigate of this insertion? We can help when the failure is obvious. However, it is ultimately component owner's responsibility to ensure the change get in. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
I'll take a look myself. |
Oh, I can see it got merged in. What has fixed the issue? |
looks like @ManickaP merged this on a different branch |
@wli3 please help me understand - does it mean the issue is still there and we need to investigate it? |
The issue is gone. I think @ManickaP did something that fixed it |
AFAIK @wli3, @janvorli we did nothing with @ManickaP; just bypassed the downgrade policy check. At the state we got into this, the real issue was already fixed. Let me look into what changed between #7490 (comment) and #7490 (comment) . |
This pull request updates the following dependencies
From https://github.com/dotnet/runtime