-
Notifications
You must be signed in to change notification settings - Fork 0
Conversation
I guess the tests are flaky... |
with: | ||
path: ${{ steps.wp_env_dir.outputs.WPENV_DIR }} | ||
key: ${{ runner.os }}-${{ hashFiles('**/.wp-env.json') }} | ||
# - name: Cache wp-env |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@n3f Is that change necessary? If so, should it be removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So the builds were failing with this in for some reason. I'm not sure if it created a timeout or if the cache was bad or what. I left the comment in because it seems like it should work (and it did work for several builds - then it broke for several). Since I removed it, all the builds have been working correctly.
@@ -120,7 +126,7 @@ public static function login_failure( string $username, \WP_Error $error ) { | |||
$failure_reason = null; | |||
} | |||
$properties = array( | |||
'$user_id' => $attempted_user->ID ? $attempted_user->ID : null, | |||
'$user_id' => (string) $attempted_user->ID ?? null, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't $attempted_user->ID ?? null
on (string)
?
I am always confused with that...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
code LGTM and tests are passing 👍
|
Fixes https://github.com/Automattic/gold/issues/525
Changes proposed in this Pull Request
Testing instructions
wp-env
(e.g.npm i && composer install && npx wp-env start
)npm run test