[meta] Known intermittent, random, and environment-specific test failures

Created on 19 November 2016, about 8 years ago
Updated 29 March 2023, over 1 year ago

This issue is intended as a tracking issue only to list all of the known intermittent test failures affecting Drupal core. Some issues are due to bugs in Drupal core; others may be due to issues with DrupalCI infrastructure.

Only open issues should be listed in the summary.

Consistent failures

Intermittent failures

  1. πŸ› DST-related test failures in FilterDateTimeTest Needs work
  2. πŸ› (canard?) Big Bos of Random Fails is ChainedFastBackend::markAsOutdated() Needs work
  3. πŸ› Random test failure in MediaStandardProfileTest::testMediaSources Fixed
  4. #3099427: [random test failure] FieldLayoutTest::testEntityView() β†’
  5. πŸ› [random test failure] Random failures building media library form after uploading image (WidgetUploadTest) Closed: cannot reproduce
  6. #3041318: Various random fails due to mis-triggered Mink deprecation error β†’
  7. #3143812: Random test failure Table 'sequences' already exists. β†’
  8. πŸ› [random test failure] Random test fail in EntityReferenceWidgetTest Active
  9. πŸ› [random test failure] LayoutBuilderQuickEditTest::testQuickEditIgnoresDuplicateFields() Active
  10. πŸ› [random test failure] EntityDisplayTest::testExtraFields() Active
  11. πŸ› [random test failure] MediaTest::testLinkManualDecorator() Fixed
  12. πŸ› [random failure] Curl error thrown for http in JSWebAssertTest Fixed
  13. ✨ Project messaging channel in core (as experimental) Fixed

Low fail rate or may be resolved

Investigation and hardening for past random failures

If your patch has an unexpected test failure

  1. Always click on the test results link to see what tests actually failed.
  2. Check the test results on https://www.drupal.org/node/3060/qa β†’ . If the same test appears to be failing on the "tested on commit" environments, HEAD may be broken.
  3. Most test failures are actually caused by bugs in patches. Even if a failure appears to be random, consider that the patch may be introducing the bug.
  4. If the test result says "CI error" or "CI aborted", that generally indicates an issue with the infrastructure and not with the patch. Wait a bit, then requeue the tests for the patch.
  5. If the test says "Fatal error" with no other information, click "View results on dispatcher", then "Console Output", then "Full log", and search on the page for "segmentation fault". #2859704: Intermittent segfaults on DrupalCI (some "did not complete due to a fatal error" with no additional info) β†’ is a known issue that may cause the test runner to report a fatal in different tests.
  6. If the test failure appears to be one of the above known failures, there is no need to add additional reports of it (unless the issue specifically requests so). Usually, once a fail is identified, Drupal.org maintainers can locate other, similar fails in server logs if needed. However, you should document on your issue which specific known issue caused the failure.
  7. If there is an unexpected test failure that is not covered by one of the above issues, file a new critical issue and add it to this issue's summary.
🌱 Plan
Status

Active

Version

10.1 ✨

Component
OtherΒ  β†’

Last updated 1 day ago

Created by

πŸ‡ΊπŸ‡ΈUnited States xjm

Live updates comments and jobs are added and updated live.
  • Triaged core major

    There is consensus among core maintainers that this is a major issue. Only core committers should add this tag.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024