-
Notifications
You must be signed in to change notification settings - Fork 7.8k
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
Run one testsuite with observers enabled in CI #13869
Conversation
@@ -184,6 +184,8 @@ jobs: | |||
-d opcache.enable_cli=1 \ | |||
-d opcache.jit_buffer_size=16M \ | |||
-d opcache.jit=tracing \ | |||
-d zend_test.observer.enabled=1 \ | |||
-d zend_test.observer.show_output=0 \ |
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.
Might it make sense to test this on x86_64 in nightly instead? E.g. .github/nightly_matrix.php
, under get_matrix_include()
, _VARIATION
. That one also runs without opcache, with opcache and with JIT(s).
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.
I personally would like to see it run in a push-job, with --repeat 2, and not nightly only.
(Because it turns out that's the configuration which catches most errors)
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.
Alright, lgtm then 🙂
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.
@bwoebi Do you really like to run this on ARM only?
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.
@dstogov I suppose we can add it on one x86 job as well. Makes sense.
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.
@bwoebi You can add it to either the nightly repeat or variation job.
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.
I also think it make more sense to setup specialized nightly jobs.
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.
@dstogov The variation job enables multiple debug checks, I think it's not too out of place there. I'm not sure there's a big benefit in testing each separately. Usually it's pretty clear what is causing the issue, from the error message.
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.
I don't know what is "variation job". Do you mean "Test", "Test Tracing JIT", etc? Of course "Test Observer" and "Tesr Observer + Function JIT" may be add as this kind of sub-jobs.
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.
php-src/.github/nightly_matrix.php
Lines 61 to 70 in dad2d56
$jobs[] = [ | |
'name' => '_VARIATION', | |
'branch' => $branch, | |
'debug' => true, | |
'zts' => true, | |
'configuration_parameters' => "CFLAGS='-DZEND_RC_DEBUG=1 -DPROFITABILITY_CHECKS=0 -DZEND_VERIFY_FUNC_INFO=1 -DZEND_VERIFY_TYPE_INFERENCE'", | |
'timeout_minutes' => 360, | |
'test_function_jit' => true, | |
'asan' => false, | |
]; |
This job runs tests with additional assertions.
Signed-off-by: Bob Weinand <bobwei9@hotmail.com>
see also: #9850 (that one can probably be closed, unless the run-test option is useful?) |
Running one full test suite with an observer doing nothing, to make sure that we do have proper coverage of them.