-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
when spawning a pty, be sure to provide & escape conhost's path #4172
Conversation
Hello @zadjii-msft! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
@msftbot make sure @miniksa signs off |
Hello @zadjii-msft! Because you've given me some instructions on how to help merge this pull request, I'll be modifying my merge approach. Here's how I understand your requirements for merging this pull request:
If this doesn't seem right to you, you can tell me to cancel these instructions and use the auto-merge policy that has been configured for this repository. Try telling me "forget everything I just told you". |
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.
Looks good.
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Huh, there's no reason x86 should have failed here. /azp run |
This is the same thing that happened to me yesterday or the day before. When I merged master INTO my branch, everything was then fine. So I just clicked the button to do that. |
(I'm having a look locally.) |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
So, it's failing with |
2aeeff4
to
f91ee42
Compare
Okay, so I'm force-merging this. I pulled the test binaries from the test machine. These are the same ones that fail in CI.
wait what, the tests passed when i force pushed it?
|
the same failure is hitting intermittently on master. |
🎉 Handy links: |
Fixes #4061.
I've tested this in multiple build and deployment configurations and placed a console application at
C:\Program.exe
before
Terminal spawns Program.exe instead of conhost.exe, and then tries to attach CMD to it.
Program.exe prints out "UNICODE. ^Z TO EXIT".
after
Everything is good.