-
-
Notifications
You must be signed in to change notification settings - Fork 703
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
Add process results and attachments in parallel #1965
Conversation
Signed-off-by: nbdnnm <nbdnnm@gmail.com>
Could you please check the results on 2.22.0 release? |
Signed-off-by: nbdnnm <nbdnnm@gmail.com>
Signed-off-by: nbdnnm <nbdnnm@gmail.com>
I have checked it with our reproduction case, 5200 tests, 10 fixtures per test, attaching it below so I guess it is still worth considering that repro case, run it like pytest --alluredir=allure-results test.py |
allure-generator/src/main/java/io/qameta/allure/core/AttachmentsPlugin.java
Outdated
Show resolved
Hide resolved
Signed-off-by: nbdnnm <nbdnnm@gmail.com>
@baev please review |
@nbdnnm The plan is to include it in the next release (I will try to land 2.23.0 sometime next week) |
Context
Related to the issue described here #1860
In our case, we use allure in pytest, and as result, we have about 2.7 GB of raw data (results+attachments) which should be generated then into a report.
There are about 15k tests, 46k attachments, 90k containers.
It takes around 50min to generate the report in the pipeline, around 30min on my mac m1.
So we dived into that and came to a quick and raw patch that gives us about 10min on mac m1.
The CPU usage jumped 10%->80%.
This PR is a proposal to discuss the approach.
@baev @eroshenkoam look forward to your feedback
Checklist