-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Allow Travis CI to build on PHP 7.4 #32289
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
Conversation
This needs to target 3.4 |
Target updated 👍 |
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'm putting this on hold because we usually don't add "allowed_job" lines: this would consume a job for every PR+merge, while they are quite precious.
Of course, once it's green and reasonably stable, we'll merge as a regular job.
Then, we'll want to rotate all jobs: deps=low should be the one running 7.4, deps=high 7.3, etc.
Could you please have a look to make this work?
Of course! |
The tests are running now. The failures are caused by unsilenced deprecation notices. |
this happened to Twig today too and was fixed by removing the use of some mocks |
We should mute this specific deprecation in the bridge I think, because many projects will be affected. /cc @greg0ire |
🤔 maybe we could add a new deprecation group called |
PHPUnit ^8.0 seems to require some missing return declarations at inherited methods, by instance:
Given that, I think this version bump can't be done in a minor release. Please, let me know how to proceed if you have elaborated some concerns about this. |
You might be able to, but it will take some black magic: symfony/src/Symfony/Bridge/PhpUnit/CoverageListener.php Lines 14 to 20 in 6811aaa
|
I built a thing! I'm a bit unsure if this should be considered bugfix or feature, and what version of the phpunit bridge is used to test 3.4 . Please advise. |
@greg0ire sorry I should have been more specific: we should mute based on the message AND the stack trace: only deprecations from phpunit should be muted. |
Oh ok it makes a lot more sense now ^^ |
I ended up picking 4.3, see link above. |
…greg0ire) This PR was merged into the 4.3 branch. Discussion ---------- [PHPUnitBridge] Mute deprecations triggered from phpunit | Q | A | ------------- | --- | Branch? | 4.3 | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | n/a | License | MIT | Doc PR | n/a Request by @nicolas-grekas here: #32289 (comment) Commits ------- a4ab13d Mute deprecations triggered from phpunit
@greg0ire, here is a sample build on |
Needs egulias/EmailValidator#203 now |
Oh wow my fix works already? I thought it would be necessary to have it land in the |
Next step unlocked. We could replace all setup/teardown methods by before/after ones, with the same as annotations. |
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'm now merging this on 3.4 only so that we can have some visibility on PHP7.4 support without consuming too many jobs.
Thank you @phansys. |
This PR was merged into the 3.4 branch. Discussion ---------- Allow Travis CI to build on PHP 7.4 | Q | A | ------------- | --- | Branch? | 3.4 | Bug fix? | no | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | n/a | License | MIT | Doc PR | n/a Commits ------- 1ca61d3 Allow Travis CI to build on PHP 7.4
Uh oh!
There was an error while loading. Please reload this page.