magento2: Can't deploy with multi-threading + compact mode
Preconditions
- Magento 2.4.3-p1 (also tested on 2.3.4)
Steps to reproduce
- Create a first theme as child of Magento/blank
- Create a second theme as child of the first theme
- Create a CSS (can be empty for the test) in the parent theme’s
web/cssfolder - Try to deploy the child theme’s static content with multi-threading and compact mode enabled :
rm -rf pub/static/frontend/ pub/static/base/ \
var/view_preprocessed/pub/static/frontend/ \
var/view_preprocessed/pub/static/base/ && \
php bin/magento setup:static-content:deploy -a frontend -t Customtheme/subtheme -f en_US --jobs 4 -s compact --no-less
Expected result
- Both themes are deployed
Actual result
- Multiple errors are triggered during the theme deployment (see screensot bellow)

You can find attached to this issue the two sample temes created without anything inside but the required files and the empty CSS on the parent theme.
Also i’ve used the official Magento Cloud Docker images to reproduce this bug.
- Severity: S0 - Affects critical data or functionality and leaves users without workaround.
- Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
- Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
- Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
- Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 1
- Comments: 17 (7 by maintainers)
Hello @engcom-Bravo ,
Indeed when I renamed the folder from
app/design/frontend/Customtheme/default/to something else (app/design/frontend/Customtheme/theme/) it worked.But this should be reported as a bug as nothing (unless I missed it?) in your documentation says that
defaultis a reserved word and shouldn’t be used for theme naming.Thank you.