Errors when using Powershell

[nrduncan]

Powershell is interpreting the output from k6 as an error. It appears that the load test is running correctly. Sample output:

          /\      |‾‾|  /‾‾/  /‾/   
     /\  /  \     |  |_/  /  / /    
    /  \/    \    |      |  /  ‾‾\  
   /          \   |  |‾\  \ | (_) | 
  / __________ \  |__|  \__\ \___/ .io

    init [----------------------------------------------------------] runner
    init [----------------------------------------------------------] options
    init [----------------------------------------------------------] executor
    init [----------------------------------------------------------]   engine
    init [----------------------------------------------------------]   collector
    init [----------------------------------------------------------]   server
  execution: local
     output: cloud (https://app.loadimpact.com/k6/runs/297936)
     script: script.js

    duration: -, iterations: -
         vus: 1, max: 25

k6 : time="2019-03-14T09:32:55-04:00" level=info msg=Running i=0 t=921.0527ms
At line:2 char:1
+ k6 run -o cloud script.js
+ ~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (time="2019-03-1...=0 t=921.0527ms:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError
 
time="2019-03-14T09:32:56-04:00" level=info msg=Running i=0 t=1.9201098s
time="2019-03-14T09:32:57-04:00" level=info msg=Running i=0 t=2.9211671s
time="2019-03-14T09:32:58-04:00" level=info msg=Running i=0 t=3.9212243s
time="2019-03-14T09:32:59-04:00" level=info msg=Running i=0 t=4.9222815s
time="2019-03-14T09:33:00-04:00" level=info msg=Running i=1 t=5.9213387s
time="2019-03-14T09:33:01-04:00" level=info msg=Running i=2 t=6.9213959s
time="2019-03-14T09:33:02-04:00" level=info msg=Running i=2 t=7.9214531s
time="2019-03-14T09:33:03-04:00" level=info msg=Running i=4 t=8.9215103s
time="2019-03-14T09:33:04-04:00" level=info msg=Running i=5 t=9.9215675s
...
time="2019-03-14T09:35:50-04:00" level=info msg=Running i=975 t=2m55.9210621s
time="2019-03-14T09:35:51-04:00" level=info msg=Running i=975 t=2m56.9211193s
time="2019-03-14T09:35:52-04:00" level=info msg=Running i=977 t=2m57.9211765s
time="2019-03-14T09:35:53-04:00" level=info msg=Running i=977 t=2m58.9212337s
time="2019-03-14T09:35:54-04:00" level=info msg=Running i=977 t=2m59.9212909s
time="2019-03-14T09:35:55-04:00" level=info msg="Test finished" i=977 t=3m0.0002954s
    init [----------------------------------------------------------] starting
    data_received..............: 1.2 MB 6.7 kB/s
    data_sent..................: 155 kB 861 B/s
    http_req_blocked...........: avg=3.48ms  min=0s    med=0s    max=3.02s p(90)=0s    p(95)=0s   
    http_req_connecting........: avg=3.48ms  min=0s    med=0s    max=3.02s p(90)=0s    p(95)=0s   
    http_req_duration..........: avg=55.79ms min=21ms  med=45ms  max=918ms p(90)=58ms  p(95)=93ms 
    http_req_receiving.........: avg=25.97µs min=0s    med=0s    max=1ms   p(90)=0s    p(95)=0s   
    http_req_sending...........: avg=1.99µs  min=0s    med=0s    max=1ms   p(90)=0s    p(95)=0s   
    http_req_tls_handshaking...: avg=0s      min=0s    med=0s    max=0s    p(90)=0s    p(95)=0s   
    http_req_waiting...........: avg=55.77ms min=21ms  med=45ms  max=918ms p(90)=58ms  p(95)=93ms 
    http_reqs..................: 1001   5.561102/s
    iteration_duration.........: avg=3.05s   min=3.02s med=3.04s max=6.07s p(90)=3.06s p(95)=3.09s
    iterations.................: 977    5.427769/s
    vus........................: 1      min=1  max=25
    vus_max....................: 25     min=25 max=25

[na--]

Powershell is interpreting the output from k6 as an error.

I think that's because, by default, k6 emits its logs to stderr (standard error). You can redirect stderr to stdout or to a file directly from PowerShell (SO question on the topic), and since k6 v0.28.0 you can also send the logs to stdout directly from k6 with the --log-output option.

So, I think we can close this issue. I see some other artifacts in the output, though those are better tracked in #1748 and might require #1376 to be solved.