pub [global] run doesn't redirect stdout/stderr?

[DartBot]

<img src="https://avatars.githubusercontent.com/u/444270?v=3" align="left" width="96" height="96"hspace="10"> Issue by seaneagan
Originally opened as dart-lang/sdk#23072

---

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.

[DartBot]

<img src="https://avatars.githubusercontent.com/u/405837?v=3" align="left" width="48" height="48"hspace="10"> Comment by zoechi

---

Probably similar to http://dartbug.com/21049

[DartBot]

<img src="https://avatars.githubusercontent.com/u/405837?v=3" align="left" width="48" height="48"hspace="10"> Comment by zoechi

---

And probably a workaround for http://dartbug.com/21564 which should be fixed.

[DartBot]

<img src="https://avatars.githubusercontent.com/u/444270?v=3" align="left" width="48" height="48"hspace="10"> Comment by seaneagan

---

I don't think it matters if the output of the process spawned by pub run is written synchonously or not, it should still be capturable by the calling process (pub run) via something like:

  Process.start(...)
    ..stdout.listen(stdout.write);
    ..stderr.listen(stderr.write);

Is pub [global] run already doing something like that?

[DartBot]

<img src="https://avatars.githubusercontent.com/u/444270?v=3" align="left" width="48" height="48"hspace="10"> Comment by seaneagan

---

Actually, there's an example right in the docs for Process.start:

Process.start('grep', ['-i', 'main', 'test.dart']).then((process) {
  stdout.addStream(process.stdout);
  stderr.addStream(process.stderr);
});

[DartBot]

<img src="https://avatars.githubusercontent.com/u/5449880?v=3" align="left" width="48" height="48"hspace="10"> Comment by iposva-google

---

Added Area-Pub, Triaged labels.

[DartBot]

<img src="https://avatars.githubusercontent.com/u/188?v=3" align="left" width="48" height="48"hspace="10"> Comment by nex3

---

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.