-
Notifications
You must be signed in to change notification settings - Fork 129
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
AutoCluster - NBomber context.StopCurrentTest() - do not save properly FinalStats #694
Comments
Hi @daveharris1 , Are you sure that the HTML report was taken from the Coordinator? I have tried to reproduce this behavior several times locally but have had no luck so far. |
I have tried to run 3 min load test with cluster of 2-3 nodes but the results are always consistent. |
Yes this is the Coordinator. This is from the generated txt that is in the same 'session' folder generated for the Coordinator with the HTML report: As mentioned on the other issues I have open, we do not wait for the scenario to complete but exit the test early via:
I am also using multiple steps in the test via https://nbomber.com/docs/using-nbomber/basic-api/step The latest run again shows a mismatch between the report generated data and what is shown in the Grafana dashboard. I have noted the RPS looks to match between the two sources. |
The following issues has been raised after talking with Anton Moldovan.
NBomber NuGet package version: 5.6.0
NBomber.Sinks.InfluxDB NuGet package version: 5.0.2
When Running NBomber via AutoCluster in a distributed manner, the generated 'Session' Coordinator reports i.e csv, HTML5 report looks to be duplicating the request count information.
This has been seen after every distributed run and doesn't seem to be affect by agent count. The data generated in the reports is at odds with what is reported via the Grafana dash board.
Example Bombing run Grafana output (after test completion):
Example of the HTML5 report showing what looks to be the duplication of requests and RPS data along with the fact the data doesn't match the Grafana output above:
The text was updated successfully, but these errors were encountered: