Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Overview
looks like 0.x is now failing since #3475584: Add support for Blocks as Components https://git.drupalcode.org/project/experience_builder/-/pipelines?page=1...
I can't get it to fail locally
So setting to needs work to alert anyone who is following this issue and might have ideas. We should probably fix in another issue
It could have been a drupal core change but I have pull the latest changes and can't get it to fail
Proposed resolution
User interface changes
Issue fork experience_builder-3486168
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
tedbowAssigned to myself but if anyone has any ideas please jump in
I am going to start by creating MR to get a better error message from this
Comment #4
tedbowok seems like 0.x is passing again?
one thing I don’t like is that the functional tests were failing on this $assert_session->statusCodeEquals(200);
just on gitlab not locally, so could have been some composer package version that wasn’t pick up temporarily or some problem with gitlabci
but because of that assert we only get
Behat\Mink\Exception\ExpectationException: Current response status code is 500, but 200 expected.
in autoupdate, in our build tests, we had some utility method to always display the page content because the 500 error doesn’t tell us anything
If you look at this pipeline for the MR found this on https://git.drupalcode.org/project/experience_builder/-/pipelines/331481
you can see composer jobs passing and then phpunit jobs failing in the same way that 0.x was
Comment #5
tedbow