An attempt to build Drupal Core with any Core patch end with error

SIMPLYEST_STAGE_PATCHING 65672ed90a5d5302cc94757d# /bin/sh -c composer global config --no-interaction allow-plugins.szeidler/composer-patches-cli true Changed current directory to /root/.composer 65672ed90a5d5302cc94757d# /bin/sh -c composer global config --no-interaction allow-plugins.cweagans/composer-patches true Changed current directory to /root/.composer 65672ed90a5d5302cc94757d# /bin/sh -c composer global require szeidler/composer-patches-cli:~1.0 Changed current directory to /root/.composer ./composer.json has been updated Running composer update szeidler/composer-patches-cli Loading composer repositories with package information Updating dependencies Lock file operations: 2 installs, 0 updates, 0 removals - Locking cweagans/composer-patches (1.7.3) - Locking szeidler/composer-patches-cli (1.0.6) Writing lock file Installing dependencies from lock file (including require-dev) Package operations: 2 installs, 0 updates, 0 removals - Downloading cweagans/composer-patches (1.7.3) - Downloading szeidler/composer-patches-cli (1.0.6) 0/2 [>---------------------------] 0% 2/2 [============================] 100% - Installing cweagans/composer-patches (1.7.3): Extracting archive - Installing szeidler/composer-patches-cli (1.0.6): Extracting archive Generating autoload files No security vulnerability advisories found. 65672ed90a5d5302cc94757d# /bin/sh -c cd stm && composer patch-enable --file="patches.json" /bin/sh: 1: cd: can't cd to stm Command Failed (Tugboat Error 1064): Exit code: 2; Command: cd stm && composer patch-enable --file="patches.json"

Comments & Activities

Issue created by @devad
Comment 12 months ago →
🇳🇿New Zealand jweowu
FWIW I was getting this problem* consistently on November 10th (Friday), and still on the 13th (Monday) when I tried again. The following day I noted that it was fixed, and so I didn't bother to raise a bug report, but I see that it's happening again and so maybe it's not actually resolved? I mention the dates just in case the maintainers are unaware that this same issue was occurring earlier.

(*) And/or similar failures. I remember the "can't cd to stm" error quoted above, but IIRC also encountered a composer failure at least one of those runs. Most of my attempts were for a Drupal Core instance with no patches.
Comment 12 months ago →
🇳🇿New Zealand jweowu
Ah, interestingly I seem to be able to build 10.1.x at the moment (including with patches), but my attempts to build 11.x (both with and without patches) have failed.

I saw the "can't cd to stm" error earlier, but my last attempt failed with:

This may be the error: 6569361f5d2bde9a88fdf200# /bin/sh -c cd "${DOCROOT}" && echo '$settings["file_private_path"] = "sites/default/files/private";' >> sites/default/settings.php /bin/sh: 1: cannot create sites/default/settings.php: Directory nonexistent
Status changed to Postponed: needs info 11 months ago2:23pm 5 January 2024
Comment 11 months ago →
🇬🇧United Kingdom rachel_norfolk UK
I’m struggling to recreate this error. Been trying with a few patches against Drupal core.

Can you confirm it is still an issue for you?
Status changed to Closed: cannot reproduce 11 months ago10:18pm 5 January 2024
Comment 11 months ago →
🇭🇷Croatia devad
I tried to reproduce. But, this time the build was successful.

Thanks for reply @rachel_norfolk. Closing...