Skip to content
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

Do not save the logs into memory using an auxiliary variable #3382

Merged
merged 2 commits into from
Nov 30, 2024

Conversation

seberm
Copy link
Collaborator

@seberm seberm commented Nov 26, 2024

Saving the huge test outputs into these Jinja2 variables causes the performance bottleneck.

Pull Request Checklist

  • implement the feature

@seberm seberm added bug Something isn't working step | report Stuff related to the report step plugin | polarion Plugins implementing the Polarion integration plugin | junit The junit report plugin labels Nov 26, 2024
@seberm seberm added this to the 1.40 milestone Nov 26, 2024
@seberm seberm changed the base branch from main to feature/enable-huge-tree-for-lxml November 26, 2024 13:56
@seberm seberm added the ci | full test Pull request is ready for the full test execution label Nov 26, 2024
@seberm seberm force-pushed the feature/enable-huge-tree-for-lxml branch from 21cfe4d to 4b5bc05 Compare November 27, 2024 14:30
@seberm seberm force-pushed the feature/fix-junit-template-performance branch from ec7bee0 to ba0684a Compare November 27, 2024 14:48
Copy link
Collaborator

@martinhoyer martinhoyer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very nice

@happz happz force-pushed the feature/enable-huge-tree-for-lxml branch from cbdb31c to a38377b Compare November 28, 2024 08:57
@seberm seberm force-pushed the feature/fix-junit-template-performance branch from ba0684a to bb73e58 Compare November 28, 2024 12:49
Base automatically changed from feature/enable-huge-tree-for-lxml to main November 28, 2024 20:51
@happz
Copy link
Collaborator

happz commented Nov 28, 2024

@seberm please, rebase, there will be some conflicts :/

Saving the **huge** test outputs into these variables causes the performance bottleneck.
@seberm seberm force-pushed the feature/fix-junit-template-performance branch from bb73e58 to c1e42ec Compare November 29, 2024 09:09
@seberm
Copy link
Collaborator Author

seberm commented Nov 29, 2024

@seberm please, rebase, there will be some conflicts :/

@happz rebased. Thanks!

@seberm seberm self-assigned this Nov 29, 2024
@happz
Copy link
Collaborator

happz commented Nov 29, 2024

@seberm I'm afraid unit tests are failing.

@seberm
Copy link
Collaborator Author

seberm commented Nov 29, 2024

@seberm I'm afraid unit tests are failing.

Thanks for the ping, it should be fixed now by 56a2407

@happz happz added the status | ready for merge The only missing piece is to do the rebase the current 'main' and let the CI finish. label Nov 29, 2024
@happz
Copy link
Collaborator

happz commented Nov 30, 2024

Unrelated failures, merging.

@happz happz merged commit 6121919 into main Nov 30, 2024
19 of 20 checks passed
@happz happz deleted the feature/fix-junit-template-performance branch November 30, 2024 13:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ci | full test Pull request is ready for the full test execution plugin | junit The junit report plugin plugin | polarion Plugins implementing the Polarion integration status | ready for merge The only missing piece is to do the rebase the current 'main' and let the CI finish. step | report Stuff related to the report step
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants