Problem/Motivation

Launching Burndown Drupal module fails with this error:

631e9273d65209e3aa555880# /bin/sh -c cd "${DOCROOT}" && composer update --no-ansi
/bin/sh: 1: cd: can't cd to /var/www/html
Command Failed (Tugboat Error 1064): Exit code (2)

Steps to reproduce

1. Go to https://simplytest.me/

2. Fill the form as follows:

  • Evaluate Drupal projects: Burndown
  • Version: 1.0.17 (^8.8 || ^9)

3. After 40% launch progress done. This error message is display. This is the challenge.

631e9273d65209e3aa555880# /bin/sh -c cd "${DOCROOT}" && composer update --no-ansi
/bin/sh: 1: cd: can't cd to /var/www/html
Command Failed (Tugboat Error 1064): Exit code (2)

This attached text file shows the full log. The error message is on the last lines. Per HarishST's comment, the same error message can be reproduced with Drupal core 9.4.5 alone.

4. The needed end result is that Burndown or Drupal launch. Without this error message.

Proposed resolution

I don't know. Any volunteer for a patch? Both me and the Ubertus.org team would be happy, as volunteer, to contribute testing and documentation, if needed.

Remaining tasks

User interface changes

API changes

Data model changes

CommentFileSizeAuthor
error---burndown---2022-09-11.txt3.51 MBfrancewhoa

Comments

Francewhoa created an issue. See original summary.

francewhoa’s picture

Issue summary: View changes
harishst’s picture

The issue is not related to Burndown module. Trying out a Drupal core (9.4.5) also throws out the same error:

631ebfdd0624940e75f9a45c# /bin/sh -c cd "${DOCROOT}" && composer update --no-ansi
/bin/sh: 1: cd: can't cd to /var/www/html

Seems like an permission issue.

francewhoa’s picture

Title: Launch Burndown Fails With Error "/bin/sh: 1: cd: can't cd to /var/www/html" » Launch Burndown or Drupal fails with error "/bin/sh: 1: cd: can't cd to /var/www/html"
francewhoa’s picture

Thanks for your comment HarishST :) I updated this ticket title to include both Drupal and Burndown

francewhoa’s picture

Priority: Normal » Major
Issue summary: View changes

I updated the ticket description to include Drupal core 9.4.5. Also bumped up the suggested priority to Major. As Drupal core is affected. Which in turn affect all Drupal 9 modules.

nerdstein’s picture

Assigned: Unassigned » nerdstein

Thanks for filing this. I accidentally pushed a regression from my last release. I'll get this cleaned up today.

francewhoa’s picture

Thanks @nerdstein for solving this mystery. And thanks for all your contributions to simplytest.me Appreciated :)

After you're done with cleaning up the good faith regression, I would be happy to contribute testing

greggmarshall’s picture

Let me know as well, I just encountered the error trying blockgroup + 9.4.5

nerdstein’s picture

Status: Active » Fixed

This should be fixed now based on the fixes pushed in #3308715

francewhoa’s picture

Thanks nerdstein :)

francewhoa’s picture

This is to confirm that simplytest.me successfully launched Burndown on Drupal 9.4.5 :)

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.