-
Notifications
You must be signed in to change notification settings - Fork 34
Restrict patch from being applied to version 2.4.3-p2. Since it's bee… #85
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
Restrict patch from being applied to version 2.4.3-p2. Since it's bee… #85
Conversation
…n resolved in the patch it self. For more information see: * magento/magento2#35341
Functional Acceptance Test Results❌ One or more functional acceptance tests have failed. PHP 7.2
PHP 7.3
PHP 7.4
PHP 8.1
Output for failed tests is below. If many tests have failed only the first 5 will be included. If you need additional information please reach out to the Magento Cloud team for more details. This comment was generated by Jenkins job magento-cloud-patches/functional build 100. |
PHP 7.2 Acceptance72CeCest OutputThis comment was generated by Jenkins job magento-cloud-patches/functional build 100. |
PHP 7.2 Acceptance72Cest OutputThis comment was generated by Jenkins job magento-cloud-patches/functional build 100. |
|
I cannot resolve this issue for php7.2 in my opinion. Could someone check it? |
|
@BarnyShergold i saw you were a pr of the previous merge. Could you look into this? I think it's important otherwise all cloud project will have a patch that should not be applied from @nathanjosiah |
|
|
@BarnyShergold the functional check doesnt seem to work for php7.2. While i dont think i did anything wrong. I just wanted to bring this too urgent notice and with the last merge i mean a previous pr that was merged in this repository. Also you helped me last time i created an pr for ece-tools. Thats why i asked you 😁. The constraint that i changed is from smaller than 2.4.3-p3 to smaller than 2.4.3-p2 is necessary. Nathan confirmed to me that this patch must not be applied for magento projects that are on 2.4.3-p2. Since it was resolved in a different way in 2.4.3-p2. I think this issue has a high priority because it must not be applied for magento 2.4.3-p2 cloud projects, while it does now. So everyone that now updates to 2.4.3-p2 will have a wrong patch added to their shop. For more info about this patch see magento/magento2#35341 Hope this clarifies my issues. Also cant seem to add any assignees to check this pr. |
I'm afraid I can't help you with the functional tests - it won't say why it's failed and I can't see any reason . I'll see if it possible to re-run but you'll have to wait for one of the main people to review. |
|
@magento run Functional Tests |
|
Could anyone look at this i think it's pretty important. |
|
In the line above the line you modified, the version should probably also be changed from |
|
Hi @leonhelmus |
|
@BaDos the Pull Request is successfully imported. |
|
@BaDos an error occurred during the Pull Request import. |
|
When will the tag 1.0.17 be available? |
|
@BaDos I really want to update to 1.0.17 |
|
@nathanjosiah Could someone make the tag available? |
|
@leonhelmus https://github.com/magento/magento-cloud-patches/tree/1.0.17 |
|
@BaDos thanks for the update :). This will prevent other people from applying the patch. |
Bump version to 1.0.24
…n resolved in the patch it self.
For more information see:
Description
Magento cloud patches apply a patch that has been resolved in magento 2.4.3-p2. According to @nathanjosiah.
Fixed Issues (if relevant)
Associated documentation updates
magento/magento2#35341
Contribution checklist