You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have created a series of K6 test that are working fine when I run them with k6 run MY_TEST.js, and these test are importing a couple local modules including one named config.js
But when I try to run the same test with k6 cloud run MY_TEST.js --local-execution I am getting:
error="GoError: the module "./config.js" was not previously resolved during initialization (__VU==0)\n"
I am unclear if there is something I am missing here or if this is running in some other directory when you use cloud run but my assumption would be the local execution flag would make it so it should run in the exact some way as k6 run would.
Not sure if it matters but I am running this on windows and any help would be appreciated.
I have created a series of K6 test that are working fine when I run them with k6 run MY_TEST.js, and these test are importing a couple local modules including one named config.js
But when I try to run the same test with k6 cloud run MY_TEST.js --local-execution I am getting:
error="GoError: the module "./config.js" was not previously resolved during initialization (__VU==0)\n"
I am unclear if there is something I am missing here or if this is running in some other directory when you use cloud run but my assumption would be the local execution flag would make it so it should run in the exact some way as k6 run would.
Not sure if it matters but I am running this on windows and any help would be appreciated.
Expected behaviour
Should run same as k6 cloud run MY_TEST.js
Actual behaviour
error="GoError: the module "./config.js" was not previously resolved during initialization (__VU==0)\n"
I am unclear if there is something I am missing here or if this is running in some other directory when you use cloud run but my assumption would be the local execution flag would make it so it should run in the exact some way as k6 run would.
The text was updated successfully, but these errors were encountered:
Brief summary
This bug created from the community page: https://community.grafana.com/t/issue-loading-local-modules-when-using-k6-cloud-run-local-execution/136919
The issue is affecting me as well as many other users. Kindly prioritise accordingly.
I have created a series of K6 test that are working fine when I run them with k6 run MY_TEST.js, and these test are importing a couple local modules including one named config.js
But when I try to run the same test with k6 cloud run MY_TEST.js --local-execution I am getting:
error="GoError: the module "./config.js" was not previously resolved during initialization (__VU==0)\n"
I am unclear if there is something I am missing here or if this is running in some other directory when you use cloud run but my assumption would be the local execution flag would make it so it should run in the exact some way as k6 run would.
Not sure if it matters but I am running this on windows and any help would be appreciated.
k6 version
v0.55.2
OS
windows 10
Docker version and image (if applicable)
No response
Steps to reproduce the problem
This bug created from the community page: https://community.grafana.com/t/issue-loading-local-modules-when-using-k6-cloud-run-local-execution/136919
The issue is affecting me as well as many other users. Kindly prioritise accordingly.
I have created a series of K6 test that are working fine when I run them with k6 run MY_TEST.js, and these test are importing a couple local modules including one named config.js
But when I try to run the same test with k6 cloud run MY_TEST.js --local-execution I am getting:
error="GoError: the module "./config.js" was not previously resolved during initialization (__VU==0)\n"
I am unclear if there is something I am missing here or if this is running in some other directory when you use cloud run but my assumption would be the local execution flag would make it so it should run in the exact some way as k6 run would.
Not sure if it matters but I am running this on windows and any help would be appreciated.
Expected behaviour
Should run same as k6 cloud run MY_TEST.js
Actual behaviour
error="GoError: the module "./config.js" was not previously resolved during initialization (__VU==0)\n"
I am unclear if there is something I am missing here or if this is running in some other directory when you use cloud run but my assumption would be the local execution flag would make it so it should run in the exact some way as k6 run would.
The text was updated successfully, but these errors were encountered: