Problem/Motivation

The "Automated Functional Testing" job retries composer require and composer install 5 times each, then carries on whatever happened. A require that never succeeds only shows up later, as an unrelated error.

The composer install loop fails all 5 attempts on every run, green ones included: once composer require -W has unpacked the recipes, the lock no longer resolves (drupal/varbase_content_base ~1.0.0 could not be found).

Steps to reproduce

Search a green job log for "composer install attempt", for example job 12798852.

Proposed resolution

Do what varbase_search_base does: fail the job after 5 failed composer require attempts, and drop the separate composer install, since require already installs what it adds.

Remaining tasks

  • ✅ File an issue
  • ❌ Addition/Change/Update/Fix
  • ❌ Testing to ensure no regression
  • ➖ Automated unit/functional testing coverage
  • ➖ Developer Documentation support
  • ➖ User Guide Documentation support
  • ➖ UX/UI designer responsibilities
  • ➖ Accessibility and Readability
  • ❌ Reviewed by a human
  • ❌ Code review by maintainers
  • ❌ Full testing and approval
  • ❌ Credit contributors
  • ❌ Review with the product owner
  • ❌ Update Release Notes
  • ❌ Release

User interface changes

  • N/A

API changes

  • N/A

Data model changes

  • N/A

Release notes snippet

  • N/A
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:

Comments

rajab natshah created an issue. See original summary.

  • rajab natshah committed eca8ef6b on 1.0.x
    ci: #3630066 Stop the functional testing CI job hiding composer failures
    
rajab natshah’s picture

Status: Active » 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.

rajab natshah’s picture

Status: Fixed » Closed (fixed)

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