Tests: Avoid using runInSeparateProcess
where possible
#2275
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.
When I first saw the
@runInSeparateProcess
in I thought it was a neat way to solve the defined constants problem. It does however come at a pretty big speed penalty. Let's avoid using it when we can.From https://github.com/Automattic/wordpress-activitypub/actions/runs/18201146182/job/51820087608
Proposed changes:
runInSeparateProcess
annotations and reorders tests to continue to work.Other information: