Closed ematta closed 1 year ago
Hi @ematta !
Thanks for reporting this. I'll take a look at it! Can you let me know if in the json
report (testrun.json
) that you generated, the mean
was also showing up as undefined (or not appearing)?
P.S. as I replied here, still having the includeFiles
in the config is probably why it's still doing the installs on Fargate!
Hey @ematta 👋, had a thought yesterday, and I believe I've managed to replicate the issue. I think the problem is that since you're using Artillery as a dependency, your lock files still kept dependant packages at an older version.
You should be able to confirm this by running cat node_modules/@artilleryio/int-core/package.json | grep version
in the path where your node_modules is (or if that doesn't work, try to find that package @artilleryio/int-core
in your node_modules, and confirm which version it has in package.json).
If the version you see there is not 2.2.0, then you won't have mean
, and that is causing the reporter to show that as undefined
.
You should be able to resolve this by making sure that your lock files are updated. If nothing else works, I believe simply reinstalling artillery (uninstall then install artillery@2.0.0-38
fresh) should work.
You were right. My version is "version": "2.2.0",
. Let me uninstall and re-install to see if the version bumps up.
So I uninstalled and re-installed artillery and I am still seeing version 2.2.0 in the new yarn install.
I think you misunderstood me @ematta - sorry if I wasn't clear. The version for that package should be 2.2.0. I meant if it's <2.2.0, then that would be the issue. Are you still getting the mean
undefined problem after reinstalling?
I was only able to replicate this when using an existing installation - the package-lock
file I had was causing the mismatch. Can you try installing Artillery from scratch in another directory and seeing if you still have the issue?
You were right. This seems to be an error with the previous version hiding in my yarn.lock file. Closing this out since this doesn't seem to be a real issue.
Version info:
Running this command:
I expected to see this happen:
The
mean
to have a numberInstead, this happened:
Mean
isundefined
Files being used: