mangled print output when tests are run using PubApp.local('test')

[zoechi]

This is the output when run by

@Task('Runn all tests')
test() => new PubApp.local('test').run(['-pvm', '-pcontent-shell']); `

 (master) $ grind test
grinder running [test]

[test]
  pub run test -pvm -pcontent-shell
00:00 0 +0: [VM] test/shared/parse_num_test.dart: parse int return null                               
    +0 ~1: [VM] test/shared/parse_num_test.dart: parse int return null                   
    Skip: enable!!!
00:00 +1 ~1: [VM] test/server/network/network_test.dart: network_test getNextFreeIpPort    
00:00 2 ~1: [VM] test/server/network/network_test.dart: network_test getNextFreeIpPort    
00:00 +41: [VM] test/server/network/network_test.dart: network_test getNextFreeIpPort    
00:00 +5 [VM] test/server/network/network_test.dart: network_test getNextFreeIpPort    
00:00 +6 ~1] test/server/network/network_test.dart: network_test getNextFreeIpPort    
00:00 +7 ~1: [VM]erver/network/network_test.dart: network_test getNextFreeIpPort    
00:00 +8 ~1: [VM] test/k/network_test.dart: network_test getNextFreeIpPort    
00:00 +9 ~1: [VM] test/serverst.dart: network_test getNextFreeIpPort    
00:00 +10 ~1: [VM] test/server/netwwork_test getNextFreeIpPort    
00:00 +11 ~1: [VM] test/server/network/neetNextFreeIpPort   
00:00 +12 ~1: [VM] test/server/network/network_Port   
00:00 +13 ~1: [VM] test/server/network/network_test.d
00:00 +14 ~1: [VM] test/server/network/network_test.dart: n
00:00 +15 ~1: [VM] test/server/network/network_test.dart: network
00:00 +16 ~1: [VM] test/server/network/network_test.dart: network_test 
00:00 +17 ~1: [VM] test/server/network/network_test.dart: network_test getNex
00:00 +18 ~1: [VM] test/server/network/network_test.dart: network_test getNextFreeI
00:00 +19 ~1: [VM] test/server/network/network_test.dart: network_test getNextFreeIpPort
00:00 +20 ~1: [VM] test/server/network/network_test.dart: network_test getNextFreeIpPort    [0m   
00:00 +21 ~1: [VM] test/server/network/network_test.dart: network_test getNextFreeIpPort   
00:00 22 ~1: [VM] test/server/network/network_test.dart: network_test getNextFreeIpPort   
00:00 +241: [VM] test/server/network/network_test.dart: network_test getNextFreeIpPort   
00:00 +25[VM] test/server/network/network_test.dart: network_test getNextFreeIpPort   
00:00 +26 ~1] test/server/network/network_test.dart: network_test getNextFreeIpPort   
00:00 +27 ~1: [VMerver/network/network_test.dart: network_test getNextFreeIpPort   
00:00 +28 ~1: ... Shellrk/network_test.dart: network_test getNextFreeIpPort   
00:00 +29 ~1: ... Shell] testdart: getParentElement simple DOM elements 
00:00 +29 ~1: All tests passed!tParentElement simple DOM elements 

finished in 5.405 seconds.

This is the output when I run pub run test without Grinder.

 (master) $ pub run test -pvm -pcontent-shell
00:00 +0 ~1: [VM] test/shared/parse_num_test.dart: parse int return null                            
  Skip: enable!!!
00:00 +29 ~1: All tests passed!                                                            

test writes the current status after each test on the same line (as long as there is no failing test).

[devoncarew]

test may not be detecting / checking for a non-interactive console?

[seaneagan]

Yeah, based on the screenshots in tests README, I think it clears part of the line on each test when you run multiple test files simultaneously. That behavior should be turned off when stodout is a pipe, but apparently pub apps have no way to check that yet:

dart-lang/test#19 (comment)

[zoechi]

Ok, thanks for investigating.
This means it will not be possible to get the same output when run via Grinder, even when this issue is fixed?

[seaneagan]

So #195 should allow at least getting streaming line output. I also filed #196 to see if it would be possible to expose the ansi escape code based interactive output of sub-processes.

[zoechi]

Haven't seen this since a long time.