Skip to content

Harden test checking for log file #111

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Jan 31, 2025
Merged

Harden test checking for log file #111

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
8783ba9
Debug failing test
swissspidy Jan 31, 2025
3bbf22c
Try workaround
swissspidy Jan 31, 2025
c1742f8
exit code
swissspidy Jan 31, 2025
fa5f833
true
swissspidy Jan 31, 2025
96824c0
Undo temp change
swissspidy Jan 31, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion features/cron.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -255,7 +255,13 @@ Feature: Manage WP-Cron events and schedules
"""
Error:
"""
And the {RUN_DIR}/server.log file should not exist

# Normally we would simply check for the log file to not exist. However, when running with Xdebug for code coverage purposes,
# the following warning might be added to the log file:
# PHP Warning: JIT is incompatible with third party extensions that override zend_execute_ex(). JIT disabled. in Unknown on line 0
# This workaround checks for any other possible entries in the log file.
When I run `awk '!/JIT/' {RUN_DIR}/server.log 2>/dev/null || true`
Then STDOUT should be empty

Scenario: Run multiple cron events
When I try `wp cron event run`
Expand Down