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

Mergeup of #625 #983

Merged
merged 5 commits into from
Feb 3, 2022
Merged

Mergeup of #625 #983

merged 5 commits into from
Feb 3, 2022

Conversation

therealryan
Copy link
Contributor

This is the same changeset as the apparently-stalled #625, but with merge conflicts resolved

The conflicts turned out to be simple:

  • Catch blocks were collapsed in master. These had been deleted in the branch anyway
  • The MethodName class has been removed, so no need to call MethodName.fromString() (or name() in the tests)

aurelien-baudet and others added 5 commits July 27, 2020 15:30
- #621: do not use test dependencies as test source directories
- #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.
 Conflicts:
	pitest-aggregator/src/main/java/org/pitest/aggregate/BlockCoverageDataLoader.java
	pitest-aggregator/src/main/java/org/pitest/aggregate/DataLoader.java
	pitest-aggregator/src/main/java/org/pitest/aggregate/MutationResultDataLoader.java

Conflicting changes were from:
  afba928 - collapsing catch blocks. These are removed in the branch
  anyway, so no change to branch to resolve the conflict - we just take
  the branch version
  8193731 - Removing methodName class. This change has been reflected
  in the branch
@hcoles
Copy link
Owner

hcoles commented Feb 3, 2022

Thanks @therealryan.

The tests around this area of the code are minimal, but that is an existing issue from when this feature was first added. If you can confirm that everthing works as expected when run against a real project I'll merge it in.

@therealryan
Copy link
Contributor Author

After:

  1. checking out this branch
  2. mvn install
  3. updating my project to use the 1.0.0-SNAPSHOT version that was generated
  4. Adding a <value>XML</value> element to plugin/configuration/outputFormats

I can confirm that report aggregation works as expected.

@hcoles hcoles merged commit 90d5df5 into hcoles:master Feb 3, 2022
@hcoles
Copy link
Owner

hcoles commented Feb 3, 2022

@therealryan Thanks, merged now.

@therealryan
Copy link
Contributor Author

Great stuff! All credit to @aurelien-baudet !

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.

3 participants