The following test is failing since yesterday:
001 Scenario: Don't trigger cron when ALTERNATE_WP_CRON is defined # features/cron.feature:357
And STDERR should contain: # features/cron.feature:386
$ wp cron test
Warning: The ALTERNATE_WP_CRON constant is set to true. WP-Cron spawning is not asynchronous.
Error: WP-Cron spawn returned HTTP status code: 404 Not Found
cwd: /tmp/wp-cli-test-run--69436005091a42.79513725/
run time: 0.38838696479797
exit status: 1
--- Expected
+++ Actual
@@ @@
-Error: WP-Cron spawn returned HTTP status code: 403 Forbidden
+Warning: The ALTERNATE_WP_CRON constant is set to true. WP-Cron spawning is not asynchronous.
+Error: WP-Cron spawn returned HTTP status code: 404 Not Found
(Exception)
Example: https://github.com/wp-cli/cron-command/actions/runs/20323320253/job/58383551450#step:10:58
No idea why, doesn't seem like something has changed.
But when I look at this test, it seems like it just requests https://example.com/wp-cron.php?doing_wp_cron= instead of a local server... Of course that will result in a 404.
The 403 expectation was added in #119, but that was quite flawed... From what I can see the test should still simply expect "WP-Cron spawning is working as expected."
The following test is failing since yesterday:
Example: https://github.com/wp-cli/cron-command/actions/runs/20323320253/job/58383551450#step:10:58
No idea why, doesn't seem like something has changed.
But when I look at this test, it seems like it just requests
https://example.com/wp-cron.php?doing_wp_cron=instead of a local server... Of course that will result in a 404.The 403 expectation was added in #119, but that was quite flawed... From what I can see the test should still simply expect "WP-Cron spawning is working as expected."