Skip to content

[PhpUnitBridge] Exclude from baseline generation deprecations triggered in legacy test #46711

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

Merged
merged 1 commit into from
Jun 19, 2022
Merged

Conversation

mondrake
Copy link
Contributor

Q A
Branch? 6.1
Bug fix? yes
New feature? no
Deprecations? no
Tickets Fix #46710
License MIT

@carsonbot carsonbot added this to the 6.1 milestone Jun 18, 2022
@mondrake mondrake changed the title Exclude from baseline generation deprecations triggered in legacy test [PhpUnitBridge] Exclude from baseline generation deprecations triggered in legacy test Jun 18, 2022
@nicolas-grekas nicolas-grekas modified the milestones: 6.1, 5.4 Jun 19, 2022
@nicolas-grekas
Copy link
Member

Thank you @mondrake.

@nicolas-grekas nicolas-grekas merged commit f034bf1 into symfony:5.4 Jun 19, 2022
@mondrake
Copy link
Contributor Author

Thanks @nicolas-grekas!

However I think we need to adjust some tests that are now failing - how do you usually do that? Revert and fix, new PR, or? Sorry I come from Drupal world, not yet accustomed to Symfony's etiquette.

@mondrake mondrake deleted the exclude-legacy branch June 20, 2022 08:29
@mondrake
Copy link
Contributor Author

Tests will be fixed in #46719 .

@wouterj
Copy link
Member

wouterj commented Jun 20, 2022

To answer your questions about the "normal process" of failing tests: Normally, we don't merge PRs that cause test failures, but sometimes we missed that a PR introduced new failing tests (I think that's what happened here).

Due to third party changes or other changes when upmerging older versions into newer branches, our branches often have a few failing tests. If you feel like it, we always welcome people submitting a PR to fix failing tests :) Otherwise, a core team member takes care of it (as the branches have to be green before releasing a new version at the end of the month).

@mondrake
Copy link
Contributor Author

Thanks @wouterj - I see fixes are already under way, so I'll just pause here.

This was referenced Jun 26, 2022
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.

4 participants