-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Fix setup upgrade command re enables caches #28491
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
Fix setup upgrade command re enables caches #28491
Conversation
Hi @AbdulRahmanAbouzaid. Thank you for your contribution
❗ Automated tests can be triggered manually with an appropriate comment:
You can find more information about the builds here ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review. For more details, please, review the Magento Contributor Guide documentation. |
@magento run all tests |
@magento run all tests |
…/github.com/AbdulRahmanAbouzaid/magento2 into fix_setup-upgrade_command_re-enables_caches
@magento run Static Tests |
@magento run Integration Tests |
@magento run Functional Tests B2B |
@magento run all tests |
@magento run all tests |
Hi @VladimirZaets, thank you for the review.
|
@VladimirZaets Could you put an appropriate label for test coverage? |
@engcom-Alfa I believe it requires automatic test, but not sure how to test CLI commands correctly |
@magento run all tests |
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.
✔ Approved.
Failing tests looks not related to changes form this PR.
Hi @ihor-sviziev, thank you for the review. |
@magento run all tests |
✔️ QA Passed The cache status has not been changed after performing Upgrade Manual testing scenario
Actual ResultThe previously disabled caches are still in Disabled status (0)
Before switching to PR
|
Hi @AbdulRahmanAbouzaid, thank you for your contribution! |
Description (*)
Fix re-enables all frontend caches after running setup:upgrade command including the disabled one BY Return them back to their old state before running setup:upgrade.
Fixed Issues (if relevant)
Manual testing scenarios (*)
1.Disable one of/all frontend caches [ layout, block_html and full_page] (for example: run
bin/magento cache:disable layout
).2. run
bin/magento setup:upgrade
.3. Run
bin/magento cache:status
and you can find that layout cache disabled.Contribution checklist (*)