Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue Loading Local Modules when using k6 cloud run –local-execution #4168

Open
bijopunnoose opened this issue Jan 9, 2025 · 0 comments
Open
Assignees

Comments

@bijopunnoose
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants