Skip to content
This repository has been archived by the owner on Feb 7, 2022. It is now read-only.

Unable to convert .jmx file to k6 using jmeter-to-k6, when using CSV dataset config element in my jmeter #20

Closed
ashadrahman opened this issue Jul 5, 2019 · 0 comments · Fixed by #21

Comments

@ashadrahman
Copy link

ashadrahman commented Jul 5, 2019

Hello All,
I'm getting below error when I'm trying to convert my jmx file to k6. Its says Cannot find module 'tinyify'
I'm not sure why this issue is occuring. Please get it resolved soon. Using Jmeter version 5.0

(node:8518) UnhandledPromiseRejectionWarning: Error: Cannot find module 'tinyify' from '/Users/ashadrahman'
at Function.module.exports [as sync] (/Users/ashadrahman/jmeter-to-k6/node_modules/resolve/lib/sync.js:71:15)
at Browserify.plugin (/Users/ashadrahman/jmeter-to-k6/node_modules/browserify/index.js:388:29)
at Promise (/Users/ashadrahman/jmeter-to-k6/src/build.js:83:13)
at new Promise ()
at bundle (/Users/ashadrahman/jmeter-to-k6/src/build.js:81:10)
at buildCompat (/Users/ashadrahman/jmeter-to-k6/src/build.js:15:12)
(node:8518) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:8518) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

@ashadrahman ashadrahman changed the title Unable to convert .jmx file to k6 Unable to convert .jmx file to k6 using jmeter-to-k6 Jul 5, 2019
@ashadrahman ashadrahman changed the title Unable to convert .jmx file to k6 using jmeter-to-k6 Unable to convert .jmx file to k6 using jmeter-to-k6, when using CSV dataset config element in my jmeter Jul 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant