-
-
Notifications
You must be signed in to change notification settings - Fork 513
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
Reports not getting generated when test cases cross certain number #2829
Comments
Try with version 3.2.5 |
Ok. Will try to accommodate new version and update here soon. |
Tried with 3.2.5 version also and waited for around 2 hours.. but reports are not generated. Our scripts stop here
After this nothing happens and the scripts are like in stalled mode. We tried running on both local and on a remote host through pipeline. |
hi, a thread dump may be interesting at this point |
When I ran with 35 test cases reports were generated
|
Let me see |
It could be memory or environment-related. We routinely generate reports for thousands of tests in a few minutes, so there is something else going on. |
True. |
ThreadDump1.txt Let me know If heap dump is also needed will share on email as the file format of is not supported here. |
OtherProcessThreadDump1.txt There were two more unknown processes running. |
Thanks. I had a quick look, but I can't see any Serenity-related activity in any of these thread dumps. |
Ok. Any suggestions..? |
We were logging a lot of data during our script execution (around 900k lines) and I tried to disable these logs to see if they made this impact on the reports and after disabling the logs I got the report generated :)
|
Interesting. 46 seconds to generate the reports sounds more normal. How were you generating the logs? |
We were retrieving logs data using Restassured library .log().all() method for logs. So I modified below statement from our code |
Still there is another culprit which is taking 20 to 30 min just to compile serenity reports and trigger email. It is an internal utility.. LOL .. I will work on it. |
We are using this library in our project for reporting and there is an issue that we found when our test cases went from 300 to 500 and above.
When I run the Runner file with a tag name having 50 to 100 test cases serenity reporting works fine and triggers the email, but when the test cases count went above a certain number like 500 (Now we have 700+) the report is not generated.
Scripts pause at the end waiting for serenity to generate the reports. Even after waiting for around 10 hours there was no luck.
Also I observed that it takes 30 min for just report generation for 200 to 300 test cases where the test cases get executed in 20 to 30 min, half of the time is consumed by serenity report generation :)
Can u please suggest us what could have gone wrong in the configuration? Or let us know if it is a genuine issue and ETA for fix.
We are using 3.1.15 version
Please note Pinaka is our internal library which is also using same serenity version.
Below are the list of dependencies from pom.xml used by our project.
Below is the reporting configuration from serenity.properties file
The text was updated successfully, but these errors were encountered: