Skip to content
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

AbdulRahmanAbouzaid
Copy link
Contributor

@AbdulRahmanAbouzaid AbdulRahmanAbouzaid commented Jun 3, 2020

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)

  1. Fixes Running bin/magento setup:upgrade re-enables layout, block_html and full_page caches #28186

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 (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds are green)

@ghost ghost added this to Pending Review in Pull Requests Dashboard Jun 3, 2020
@m2-assistant
Copy link

m2-assistant bot commented Jun 3, 2020

Hi @AbdulRahmanAbouzaid. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE,
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests

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.

@AbdulRahmanAbouzaid
Copy link
Contributor Author

@magento run all tests

@AbdulRahmanAbouzaid
Copy link
Contributor Author

@magento run all tests

@AbdulRahmanAbouzaid
Copy link
Contributor Author

@magento run Static Tests

@AbdulRahmanAbouzaid
Copy link
Contributor Author

@magento run Integration Tests

@AbdulRahmanAbouzaid
Copy link
Contributor Author

@magento run Functional Tests B2B

@AbdulRahmanAbouzaid
Copy link
Contributor Author

@magento run all tests

@ghost ghost added the Priority: P3 May be fixed according to the position in the backlog. label Jul 21, 2020
@VladimirZaets
Copy link
Contributor

@magento run all tests

@ghost ghost moved this from Pending Review to Ready for Testing in Pull Requests Dashboard Aug 19, 2020
@ghost ghost assigned VladimirZaets Aug 19, 2020
@magento-engcom-team
Copy link
Contributor

Hi @VladimirZaets, thank you for the review.
ENGCOM-8029 has been created to process this Pull Request
✳️ @VladimirZaets, could you please add one of the following labels to the Pull Request?

Label Description
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests

@engcom-Alfa
Copy link
Contributor

engcom-Alfa commented Aug 19, 2020

@VladimirZaets Could you put an appropriate label for test coverage?
Thanks!

@ihor-sviziev
Copy link
Contributor

@engcom-Alfa I believe it requires automatic test, but not sure how to test CLI commands correctly

@ihor-sviziev ihor-sviziev added Auto-Tests: Covered All changes in Pull Request is covered by auto-tests and removed Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests labels Sep 16, 2020
Copy link
Contributor

@ihor-sviziev ihor-sviziev left a 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.

@ghost ghost moved this from Review in Progress to Ready for Testing in Pull Requests Dashboard Sep 16, 2020
@magento-engcom-team
Copy link
Contributor

Hi @ihor-sviziev, thank you for the review.
ENGCOM-8029 has been created to process this Pull Request

@ihor-sviziev ihor-sviziev added the Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. label Sep 17, 2020
@ihor-sviziev
Copy link
Contributor

@magento run all tests

@engcom-Bravo engcom-Bravo self-assigned this Sep 23, 2020
@engcom-Bravo
Copy link
Contributor

✔️ QA Passed

The cache status has not been changed after performing Upgrade

Manual testing scenario

  1. Disable block_html full_page layout using the following command
    bin/magento cache:disable block_html full_page layout
  2. Run bin/magento cache:status and assert that following are set to 0
    layout: 0
    block_html: 0
    full_page: 0
  3. Upgrade magento instance using bin/magento setup:upgrade
  4. Check the cache status using bin/magento cache:status

Actual Result

The previously disabled caches are still in Disabled status (0)

Current status:
                        config: 1
                        layout: 0
                    block_html: 0
                   collections: 1
                    reflection: 1
                        db_ddl: 1
               compiled_config: 1
                           eav: 1
         customer_notification: 1
            config_integration: 1
        config_integration_api: 1
                     full_page: 0
             config_webservice: 1
                     translate: 1

Before switching to PR

Current status:
                        config: 1
                        layout: 1
                    block_html: 1
                   collections: 1
                    reflection: 1
                        db_ddl: 1
               compiled_config: 1
                           eav: 1
         customer_notification: 1
            config_integration: 1
        config_integration_api: 1
                     full_page: 1
             config_webservice: 1
                     translate: 1

@engcom-Bravo engcom-Bravo moved this from Ready for Testing to Testing in Progress in Pull Requests Dashboard Sep 23, 2020
@engcom-Bravo engcom-Bravo added Progress: ready for testing QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope and removed Progress: testing in progress labels Sep 23, 2020
@engcom-Bravo engcom-Bravo moved this from Testing in Progress to Extended Testing (optional) in Pull Requests Dashboard Sep 23, 2020
@engcom-Bravo engcom-Bravo moved this from Extended Testing (optional) to Merge in Progress in Pull Requests Dashboard Sep 23, 2020
@magento-engcom-team magento-engcom-team merged commit a85f600 into magento:2.4-develop Sep 24, 2020
@m2-assistant
Copy link

m2-assistant bot commented Sep 24, 2020

Hi @AbdulRahmanAbouzaid, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

@ghost ghost moved this from Merge in Progress to Recently Merged in Pull Requests Dashboard Sep 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Award: bug fix Component: Setup help wanted Partner: Pinpoint partners-contribution Pull Request is created by Magento Partner Priority: P3 May be fixed according to the position in the backlog. Progress: accept QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4 Risk: medium Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
Pull Requests Dashboard
  
Recently Merged
Development

Successfully merging this pull request may close these issues.

Running bin/magento setup:upgrade re-enables layout, block_html and full_page caches
8 participants