-
Notifications
You must be signed in to change notification settings - Fork 53
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
App stdout leaks to XHarness stderr #108
Comments
So it looks like the output is in &2, so 2>/dev/null fixes this, but still looking how it gets there |
I will have another stab at this one - it pains me so much that I cannot figure it out.. |
Confirmed this with the latests master when running on the simulator. Does not happen on device. |
I originally thought it is happening because of these lines: xharness/src/Microsoft.DotNet.XHarness.iOS/AppRunner.cs Lines 238 to 249 in 7f79598
In Xamarin, there was also redirection of stdout argument to the stdout. I removed that and now everything is sent to our stderr, which would correspond with the And also based on ProcessManager, everything should be redirected to the Log that is supplied. |
Another observation: If I call |
Part of the stdout that is the app writing and is received in XHarness through the TCP listener is displayed in stdout of XHarness. Only stuff logged through
ILogger
should be displayed.Actual:
Expected:
The text was updated successfully, but these errors were encountered: