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.

Sign up for GitHub

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

Jump to bottom

PHPUnit 9.6: Generate code coverage report in PHP format as first in list to avoid serializing cache data #5508

Merged
merged 1 commit into from
Sep 12, 2023
Merged

PHPUnit 9.6: Generate code coverage report in PHP format as first in list to avoid serializing cache data #5508

merged 1 commit into from
Sep 12, 2023

Conversation

Slamdunk
Copy link
Contributor

This is part of sebastianbergmann/php-code-coverage#1009

I'm going to open a similar PR for v10 branch

@Slamdunk Slamdunk mentioned this pull request Sep 12, 2023
Closed
3 tasks
@sebastianbergmann sebastianbergmann merged commit a3ad9d1 into sebastianbergmann:9.6 Sep 12, 2023
@Slamdunk Slamdunk deleted the cc_php_report_without_cache branch September 12, 2023 13:54
@sebastianbergmann sebastianbergmann changed the title [9.x] CodeCoverage: process PHP report as first in list to avoid serializing cache data Generate code coverage report in PHP format as first in list to avoid serializing cache data Sep 12, 2023
@sebastianbergmann sebastianbergmann changed the title Generate code coverage report in PHP format as first in list to avoid serializing cache data PHPUnit 9.6: Generate code coverage report in PHP format as first in list to avoid serializing cache data Sep 12, 2023
@sebastianbergmann sebastianbergmann added the type/performance Issues related to resource consumption (time and memory) label Sep 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
type/performance Issues related to resource consumption (time and memory)
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@Slamdunk @sebastianbergmann