Problem/Motivation

See https://git.drupalcode.org/issue/drupal-3346394/-/jobs/6063361 for an example.

I think this is packagist/github related which might be a general gitlab issue #3445532: Random HTTP timeouts for GitLab CI jobs, but would be good to pin down if we can.

See https://project.pages.drupalcode.org/flaky_tests_dashboard/ which shows recent failures. Stats as at Aug 18 2025:

PackageInstallSubmoduleTest: 23
PackageInstallTest: 21
PackageUpdateTest: 18

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Issue fork drupal-3508109

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

catch created an issue. See original summary.

catch’s picture

catch
he/him
Primary language English
commented
Status: Active » Closed (duplicate)

Duplicate of #3497701: [random test failure] PackageUpdateTest::testPackageUpdate

mstrelan’s picture

mstrelan commented
Issue summary: View changes
Status: Closed (duplicate) » Active

Re-opening this as it's still occurring after #3508109: [random test failure] Package manager random build failures.

Adding a more recent job - https://git.drupalcode.org/issue/drupal-3346394/-/jobs/6063361

mstrelan opened merge request !13018

mstrelan’s picture

mstrelan commented

It failed a couple times for the first runs, but the overall run timed out so we didn't get to see the full logs. Now it's passing with 75 runs. I suspect it's probably intermittent. Maybe we'll get different results if we rerun tomorrow.

It's worth noting that the repeat test job configuration had different cpu request and concurrency than the build job, so I've updated those to match.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.

dww’s picture

dww
we/he/they
commented

Hit this again at https://git.drupalcode.org/project/drupal/-/jobs/9497402

This does still seem to be a regular source of failures. Can we skip these for now? Package Manager is still "experimental", after all. We could make fixing these tests a critical blocker to marking that module stable. But meanwhile, the rest of core development continues to suffer while these tests intermittently fail.

dww’s picture

dww
we/he/they
commented

Also https://git.drupalcode.org/project/drupal/-/jobs/9494209 from the same issue (yesterday). In both pipelines, both of these failed:

  • PackageInstallTest
  • PackageInstallSubmoduleTest
dww’s picture

dww
we/he/they
commented

Opened #3586618: Skip randomly failing Package Manager build tests as a child, with a trivial MR to skip the 3 offenders for now, with @todo pointing here to re-enable them.

Also added this issue as a stable blocker for Package Manager at #3319030-269: Drupal Core Roadmap for Package Manager and Update Manager

dww’s picture

dww
we/he/they
commented

Much of this might be solved by #3592813: Replace usage of State in package_manager tests with KeyValue