Fixes Scrutinizer integration (mostly failing tests) #682
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
because it keeps failing due to not enough memory: https://scrutinizer-ci.com/g/smalot/pdfparser/inspections/2ffb5293-e8a3-422b-a726-48229a359df4
j0k3r
approved these changes
Feb 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of pull request
About
This PR is the successor of #412 and re-establishes Scrutinizer integration. Our tests were failing because of insufficient memory. I changed configuration file to provide test process more memory. Nice side effect, because of additional changes Scrutinizer runs faster now 🚀.
Scrutinizer build reference: https://scrutinizer-ci.com/docs/configuration/build_reference
Latest working Scrutinizer test: https://scrutinizer-ci.com/g/smalot/pdfparser/inspections/eed3683a-fc39-4819-90a2-3e626479062b