grafana/k6-intellij-plugin

commond line is not right

lemual opened this issue · 3 comments

lemual commented 
      /\      |‾‾|  /‾‾/  /‾/   
 /\  /  \     |  |_/  /  / /    
/  \/    \    |      |  /  ‾‾\

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

init [----------------------------------------------------------ERRO[0001] GoError: The moduleSpecifier "https://jslib.k6.io/k6-summary/0.0.1/index.js" couldn't be retrieved from the resolved url "https://jslib.k6.io/k6-summary/0.0.1/index.js". Error : "Get https://jslib.k6.io/k6-summary/0.0.1/index.js: dial tcp 18.65.191.101:443: connect: bad file descriptor"
lemual commented

why my command line is k6 run /var/folders/f2/l7s1_34s1w13qx76ycxyy1v00000gp/T/disk_replica_describe.js

lemual commented

I put script in a java project，the k6 script path is ： /Users/xxx/Documents/xxxcode/xxxProject/src/test/k6/disk_replica_describe.js

image

then , i got this :

k6 run /var/folders/f2/l7s1_34s1w13qx76ycxyy1v00000gp/T/disk_replica_describe.js
Testing started at 4:57 下午 ...

      /\      |‾‾|  /‾‾/  /‾/   
 /\  /  \     |  |_/  /  / /    
/  \/    \    |      |  /  ‾‾\

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

init [----------------------------------------------------------ERRO[0001] GoError: The moduleSpecifier "https://jslib.k6.io/k6-summary/0.0.1/index.js" couldn't be retrieved from the resolved url "https://jslib.k6.io/k6-summary/0.0.1/index.js". Error : "Get https://jslib.k6.io/k6-summary/0.0.1/index.js: dial tcp 18.65.191.31:443: connect: bad file descriptor"
mbolotov commented

Hi @lemual!
Is the issue is still actual for you?

why my command line is k6 run /var/folders/f2/l7s1_34s1w13qx76ycxyy1v00000gp/T/disk_replica_describe.js

That's because the plugin wrap the run script with some utility code to be able to parse and show each of the thresholds as a separate test in the IDE test view.
This behavior can be changed by the Show thresholds as tests checkbox in a run configuration.

dial tcp 18.65.191.31:443: connect: bad file descriptor"

This looks like you had some connectivity issue.
Are you able to reproduce the problem now?