Skip to content

Repeat all tests, improve JIT coverage #18493

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.

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

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Conversation

danog
Copy link
Contributor

@danog danog commented May 4, 2025

Split from #12406

@danog danog requested review from bukka and TimWolla as code owners May 4, 2025 15:26
@danog danog marked this pull request as draft May 4, 2025 15:31
Copy link
Member

@iluuu1994 iluuu1994 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR! And sorry for the late review. If you can take care of the failing tests, I'd be in favor of this, assuming it doesn't significantly increase CI time. Might be good to confirm that with 2-3 test runs. We should also check nightly, which runs many slow tests, so the added time there might be bigger.

If that's ok, we can also drop the --repeat 2 test from nightly, as it wouldn't add any value anymore.

- name: _REPEAT
debug: true
zts: false
run_tests_parameters: --repeat 2
timeout_minutes: 360
test_function_jit: true
asan: false

@@ -42,6 +42,7 @@ runs:
export SKIP_IO_CAPTURE_TESTS=1
export STACK_LIMIT_DEFAULTS_CHECK=1
sapi/cli/php run-tests.php -P -q ${{ inputs.runTestsParameters }} \
${{ inputs.jitType == 'disable' && '' || '--repeat 2' }} \
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Various opcache things are also affected by --repeat 2, so IMO it would just make sense to always pass this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants