Skip to content

Build/Test Tools: Remove the unused PHPUnit profiler - #13092

Open
lancewillett wants to merge 1 commit into
WordPress:trunkfrom
lancewillett:chore/65888-remove-unused-wp-profiler
Open

Build/Test Tools: Remove the unused PHPUnit profiler#13092
lancewillett wants to merge 1 commit into
WordPress:trunkfrom
lancewillett:chore/65888-remove-unused-wp-profiler

Conversation

@lancewillett

Copy link
Copy Markdown
Member

Trac ticket: https://core.trac.wordpress.org/ticket/65888

What this changes

Removes the unused tests/phpunit/includes/wp-profiler.php file.

The profiler has no callers and is never loaded by the PHPUnit bootstrap. Its object-cache instrumentation also depends on properties that are no longer available.

Removing it prevents future maintenance work on test tooling that cannot run. If profiling is needed later, it can be built against the current test suite and object-cache APIs.

Testing

  • git diff --check passed.
  • Confirmed no references to wp-profiler, WPProfiler, or its wppf_*() helpers remain.
  • Confirmed the PHPUnit bootstrap does not load the profiler.

No runtime tests were added because this removes unreachable tooling.

@github-actions

Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props lancewillett.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@github-actions

Copy link
Copy Markdown

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

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.

1 participant