-
Notifications
You must be signed in to change notification settings - Fork 1.7k
pub [global] run doesn't redirect stdout/stderr? #23072
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
Comments
This comment was originally written by @zoechi Probably similar to http://dartbug.com/21049 |
This comment was originally written by @zoechi And probably a workaround for http://dartbug.com/21564 which should be fixed. |
This comment was originally written by @seaneagan I don't think it matters if the output of the process spawned by Process.start(...) Is pub [global] run already doing something like that? |
This comment was originally written by @seaneagan Actually, there's an example right in the docs for Process.start: Process.start('grep', ['-i', 'main', 'test.dart']).then((process) { |
I can't reproduce this on Linux. It's piping the output just fine for me. What version of the SDK are you using? Can you reproduce this with a simple print statement in a script run via "pub run"? How about not run via "pub run"? Can you pipe just the stderr using "2>"? Added NeedsInfo label. |
This issue has been moved to dart-lang/pub#4. |
This issue was originally filed by @seaneagan
Tried doing:
pub run unittest:unittest > out.txt
The output gets printed to the console, and not to out.txt. Presumably pub run is not redirecting the stdout/stderr of the dart script it is running to its own stdout/stderr?
I'm on windows.
The text was updated successfully, but these errors were encountered: