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

fix(report-aggregate) Fix report aggregation #625

Merged
merged 4 commits into from
Feb 3, 2022

Conversation

aurelien-baudet
Copy link
Contributor

@dan323
Copy link

dan323 commented Feb 1, 2020

I would really appreciate if we could have the aggregation fixed

@aurelien-baudet
Copy link
Contributor Author

@hcoles Could you review the PR and merge it if it is OK for you ?

Also for the new score calculation, I could add some screenshots and examples to illustrate the interest if you want

- hcoles#621: do not use test dependencies as test source directories
- hcoles#622: use the name of the mutator (it is not a class name written in mutations.xml)
In a real world project with many submodules and particularly a module that has dependencies to other modules, the generated reports can be quite heavy (100MB+). When these reports are parsed using current XML parser, report aggregation fails with GC overhead limit or OutOfMemoryError due to loading of the whole XML data in memory. The new implementation uses StAX in order to avoid loading the whole XML data in memory.
@aurelien-baudet aurelien-baudet force-pushed the fix/report-aggregation branch from 77a5b7e to 1cf7d55 Compare July 28, 2020 04:41
@aurelien-baudet
Copy link
Contributor Author

@hcoles I have rebased the PR with latest changes to fix report aggregation.
I also separate the commit for a new mutation score for multi-project aggregation (I will create another PR for this).

Can you merge with master ?

@tijanssen
Copy link

I also would like to see this fixed.

@hcoles
Copy link
Owner

hcoles commented Nov 22, 2021

@aurelien-baudet Sorry for the silence. If you can resolve the conflicts again and confirm it works, I'll merge this in.

@aurelien-baudet
Copy link
Contributor Author

Sorry but I have currently no time. Moreover, I rebased the code 3 times to resolve conflicts but it had never been merged...

@therealryan therealryan mentioned this pull request Feb 2, 2022
hcoles added a commit that referenced this pull request Feb 3, 2022
@hcoles hcoles merged commit 888be38 into hcoles:master Feb 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants