From 2c2c9dba6abb6ceadf9d93246d600bf0e90a808d Mon Sep 17 00:00:00 2001 From: Rostislav Wolny Date: Fri, 20 May 2022 13:29:12 +0200 Subject: [PATCH] Make sure WP Cron is not locked when acceptance tests start Action Scheduler uses WP Cron as trigger. When it is initially locked it takes more time for Action Scheduler to start and some tests that rely on background job fail with timeout. [MAILPOET-4274] --- mailpoet/tests/_support/DefaultsExtension.php | 3 +++ 1 file changed, 3 insertions(+) diff --git a/mailpoet/tests/_support/DefaultsExtension.php b/mailpoet/tests/_support/DefaultsExtension.php index 23582ab6bc..a5022107de 100644 --- a/mailpoet/tests/_support/DefaultsExtension.php +++ b/mailpoet/tests/_support/DefaultsExtension.php @@ -47,6 +47,9 @@ class DefaultsExtension extends Extension { global $wp_rewrite; // phpcs:ignore Squiz.NamingConventions.ValidVariableName.MemberNotCamelCaps $wp_rewrite->init(); // phpcs:ignore Squiz.NamingConventions.ValidVariableName.MemberNotCamelCaps $wp_rewrite->flush_rules(); // phpcs:ignore Squiz.NamingConventions.ValidVariableName.MemberNotCamelCaps + + // Make sure WP cron is not locked so that tests that rely on it don't timeout + delete_transient('doing_cron'); } private function setupWooCommerce() {