-
Notifications
You must be signed in to change notification settings - Fork 9.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
Performance toolkit exits before running any scenarios #21106
Comments
Hi @sshymko. Thank you for your report.
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
For more details, please, review the Magento Contributor Assistant documentation. @sshymko do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?
|
@kandy |
@sshymko can you attach the jmx file you use ? thanks |
@pmouawad |
@pmouawad |
Thanks, any way to provide to me an access to your instance or a docker image or any other alternative ? thanks |
Hi @engcom-backlog-nazar. Thank you for working on this issue.
|
@pmouawad |
It would be better if you let it live until 23h30 Paris Timezone, it’s 9am now. I am working for a customer, not sure I can dedicate time today before 20h30 |
@sshymko Looks like there is an issue of our Jmeter configuration. If loops count < 2 it will not run any scenario. |
@kandy |
@kandy |
@kandy |
@sshymko Looks like it's strange behavior in case Thread Group with Throughput Controler and throughput less than 100% work. The scenario with 100 throughput work with 1 loop too. |
@kandy |
Hello, This is expected behavior.
@kandy , if I can help on the test plan let me know where to make a kind of review. I had reported following issue but AFAICU ,nothing was taken into account: |
I see a potential issue in: on second iteration, editProductList is null Should it be ? ` ` |
Also be aware that with upgrade of Beanshell version, it became more strict and you need to declare variables. Anyway I suggest you move out of Beanshell, javascript which break scalability of JMeter |
All right, I'm shutting down the test instance 3.85.65.228. |
HI @sshymko thank you for you report, i' closing this on comment -> #21106 (comment) |
@engcom-backlog-nazar |
@sshymko so how we can fix this in magento ? if problem not in magento codebase ? |
@engcom-backlog-nazar, maybe you should open another issue to fix issues in test plan. See #21106 (comment) and other performance issues. Thanks |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions! |
Hi @sshymko. Thank you for your report and collaboration! The related internal Jira ticket The fix will be available with the upcoming |
The Magento Performance Toolkit is unable to run against a vanilla Magento 2 instance installed from scratch with the required fixture data. It successfully completes the preliminary preparation steps, but never gets to execute any frontend scenarios. JMeter exits without any errors.
Preconditions (*)
Steps to reproduce (*)
Expected result (*)
Actual result (*)
jmeter.log
jmeter-results.jtl
The text was updated successfully, but these errors were encountered: