[2.2.0-RC2.2] Static content deploy 'quick' strategy acts like 'standard' strategy

[hostep]

Preconditions

Steps to reproduce

1. Install Magento 2.2.0-rc22 or 2.2.7 or 2.3.0 or 2.4.3 or 2.4-develop using composer
2. Add 2 language packs using composer: composer require honl/magento2-nl-nl imaginaerum/magento2-language-fr-fr
3. Run bin/magento setup:upgrade
4. Create 2 different storeviews in the backend and set the Locale configuration to Dutch (Netherlands) and French (France) for those 2 storeviews
5. Reindex & flush the caches
6. Run: rm -R var/view_preprocessed/* pub/static/* (so we start from a clean slate)
7. Run: php bin/magento setup:static-content:deploy -s standard -f -t Magento/luma nl_NL fr_FR
8. Results:

Deploy using standard strategy
frontend/Magento/blank/nl_NL            2083/2083           ============================ 100% %  24 secs
frontend/Magento/blank/fr_FR            2083/2083           ============================ 100% %  26 secs
frontend/Magento/luma/nl_NL             2098/2098           ============================ 100% %  29 secs
frontend/Magento/luma/fr_FR             2098/2098           ============================ 100% %  29 secs

Execution time: 114.57253885269165

9. Run: rm -R var/view_preprocessed/* pub/static/* (so we start from a clean slate)
10. Run: php bin/magento setup:static-content:deploy -s quick -f -t Magento/luma nl_NL fr_FR
11. Results:

Deploy using quick strategy
frontend/Magento/blank/nl_NL            2083/2083           ============================ 100% %  25 secs
frontend/Magento/blank/fr_FR            2083/2083           ============================ 100% %  26 secs
frontend/Magento/luma/nl_NL             2098/2098           ============================ 100% %  31 secs
frontend/Magento/luma/fr_FR             2098/2098           ============================ 100% %  31 secs

Execution time: 119.81762409210205

Expected result

1. As advertised in the devdocs, the quick strategy should run a lot faster then the standard strategy when using multiple locale's

Actual result

1. Quick strategy behaves the same as standard strategy

[misha-kotov]

Thanks for reporting, internal issue is MAGETWO-72300

[magento-engcom-team]

Hi @TomashKhamlai. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if your want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 3. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

[hostep]

@engcom-Alfa: why exactly did you remove the "Confirmed" label again, and why did @engcom-Hotel remove their assignment?

I'm afraid that this ticket will now end up in a state that it will no longer be processed in the future ...

[m2-assistant]

Hi @engcom-Delta. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Delta]

Hi @hostep ,
The issue is reproducible with the given steps on Magento 2.4 Develop. Hence Marking the issue 'Issue Confirmed'.

Steps followed:

1. Install Magento 2.2.0-rc22 or 2.2.7 or 2.3.0 or 2.4.3 or 2.4-develop using composer
2. Add 2 language packs using composer: composer require honl/magento2-nl-nl imaginaerum/magento2-language-fr-fr
3. Run bin/magento setup:upgrade
4. Create 2 different storeviews in the backend and set the Locale configuration to Dutch (Netherlands) and French (France) for those 2 storeviews
5. Reindex & flush the caches
6. Run: rm -R var/view_preprocessed/* pub/static/* (so we start from a clean slate)
7. Run: php bin/magento setup:static-content:deploy -s standard -f -t Magento/luma nl_NL fr_FR

Results:

[github-jira-sync-bot]

❌ Something went wrong. Cannot create Jira issue.

[hostep]

Thanks, it's great to see that the majority of time spend on this issue in the last 5 years, was trying to reproduce it instead of trying to fix it.

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.magento.com/browse/AC-2551 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @engcom-Delta. Thank you for verifying the issue.
Issue Available: @engcom-Delta, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.