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

Unhandled promise rejection for the full.jmx example #48

Open
suntong opened this issue Oct 7, 2021 · 0 comments
Open

Unhandled promise rejection for the full.jmx example #48

suntong opened this issue Oct 7, 2021 · 0 comments

Comments

@suntong
Copy link

suntong commented Oct 7, 2021

Describe the bug

Using jmeter-to-k6 on the full.jmx example from
https://github.com/grafana/jmeter-to-k6/blob/master/example/full.jmx
will yield "Unhandled promise rejection." error.

To Reproduce
Steps to reproduce the behavior:

  1. jmeter-to-k6 -o k6 full.jmx

Expected behavior

JMeter to k6 JS converted successful.

See the below Logs for details.

Environment

Logs
$ jmeter-to-k6 -o k6 full.jmx 
(node:8057) 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(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:8057) [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.

$ jmeter-to-k6 -o k6 full.jmx --unhandled-rejections=strict
(node:8080) 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(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:8080) [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.

$ find k6/
k6/
# should have some files generated
$ node -v; npm -v;
v14.16.1
6.14.12

$ apt-cache policy nodejs
nodejs:
  Installed: 14.16.1-1nodesource1
  Candidate: 14.17.0-1nodesource1
  Version table:
     14.17.0-1nodesource1 500
        500 https://deb.nodesource.com/node_14.x buster/main amd64 Packages
 *** 14.16.1-1nodesource1 100
        100 /var/lib/dpkg/status
     12.21.0~dfsg-4 80
         80 http://deb.debian.org/debian bullseye/main amd64 Packages
     10.24.0~dfsg-1~deb10u1 500
        500 http://deb.debian.org/debian buster/main amd64 Packages
        500 http://security.debian.org/debian-security buster/updates/main amd64 Packages

$ uname -rm
4.4.0-19041-Microsoft x86_64

Additional context

N.A.

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

No branches or pull requests

1 participant