phpunit tests running again#22
Open
kilgore5 wants to merge 11 commits into
Open
Conversation
added 11 commits
January 24, 2024 16:13
``` Error: Version mismatch detected for the PHPUnit Polyfills. Please ensure that PHPUnit Polyfills 1.1.0 or higher is loaded. Found version: 1.0.1 ```
$this-> factory was null
…efined property: WP_Error::$taxonomy`
… be different for local dev?
This was referenced Jan 25, 2024
This was referenced Jan 25, 2024
This file contains hidden or 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
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.
Get phpunit tests running again.
tests were running cleanly here: a46c4e0 but then mysteriously started giving an error in the next commit 4695fe4 with no changes
Error is
ElasticsearchTest::test_store_menu Undefined property: WP_Error::$taxonomyBacktrace
1) ElasticsearchTest::test_store_menu Undefined property: WP_Error::$taxonomy
after investigation it appears to be an error in Yoast that will hopefully be solved with an upgrade
get_terms, but this seems to work fine when queried directly via WP