-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Forward thresholds execution results when running k6 -o cloud scripts.js
#2626
Comments
Hmm is this a regression? IIRC this used to work with old k6 versions, and the code still seems to be in the cloud output 😕 See: Line 296 in 1e84682
Lines 682 to 710 in 1e84682
Line 141 in 1e84682
|
Ah, so the actual task is about the metric values that are compared to the threshold constraints, since we only send the threshold names and their pass/fail status at the moment: Line 40 in 1e84682
But then this is a duplicate of this older issue, so I'll close it: #1956 |
Feature Description
As of this writing, when k6 is run with its output set to the cloud (
k6 run -o cloud script.js
), it observes the same behavior as whenk6 run
is executed, and does not forward its thresholds results to the cloud backend. It results in thresholds results not being displayed in k6 cloud's web interface because their result were simply not sent.In an ideal state, we would prefer for
k6 run -o cloud
to evaluate thresholds locally as it is the case currently, but we would also like it to include the results of the thresholds' execution in the output and forward it to the cloud to be able to interpret and display them.Suggested Solution (optional)
It is yet unclear how we would address this, and will probably involve some non OSS work behind closed doors.
Already existing or connected issues / PRs (optional)
The text was updated successfully, but these errors were encountered: