You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Refactor group() and check() tight coupling with the VU.State #2869
This tight coupling is preventing us from implementing group() and check() purely in JavaScript. It is also preventing us from implementing similar functions, but with better UX (e.g. #1066, #2865) or that work better with async / await (#2848, #2728)
The tight coupling can be removed with only a very small loss of efficiency, by just having the MetricEngine process check and group_duration metrics as they appear and group them based on their group tag. Here is what basically needs to be removed:
Activity
k6.check: Fix returned values when iteration is ending
k6.check: Fix returned values when iteration is ending (#2915)
olegbespalov commentedon Nov 16, 2023
For the record. After an internal discussion, we decided to clean a milestone since the issue was jumping between milestones without completion.
Once we determine which milestone it lands, we set the right one.
Refactor group and check to not be tightly coupled (grafana#3750)