Problem

The phpunit job is red on the 2.x branch of lupus_decoupled_starter. The two reported pipelines are the same failure on the same commit (5d627e6c), seen on two consecutive nightly runs:

https://git.drupalcode.org/project/lupus_decoupled_starter/-/pipelines/8... (2026-06-19)
https://git.drupalcode.org/project/lupus_decoupled_starter/-/pipelines/8... (2026-06-15)

All other stages (cspell, eslint, phpstan, phpcs, composer-lint, composer) pass. Only phpunit fails, on a single test.

Issue fork lupus_decoupled_starter-3604188

Command icon 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:

About issue forks

Comments

fago created an issue. See original summary.

fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Active » Needs review

Found the problem: The recipe ships the Canvas content template canvas.content_template.node.page.full, whose component tree pins extjs.base_heading to component version de8003a71f22746e. The installed extjs.base_heading component config entity now only offers version ef92b032e346eabc.

The component version hash drifted with changes in Canvas 1.5. It's not a problem for existing installs, since both versions will be there, but for new installs only the new version hash will exist. Let's udpate version and requre canvas_extjs +1.2 which is canvas +1.5

fago’s picture

fago
Primary language German
Location Vienna
commented

https://git.drupalcode.org/project/lupus_decoupled_starter/-/merge_reque...

fago closed merge request !12

fago opened merge request !12

fago opened merge request !13

  • fago committed f420bad7 on 2.x 
    fix: #3604188 PHPUnit test fail with Canvas 1.5

By: fago
fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Needs review » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

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