Problem/Motivation

#3410476: Add event for statement execution failure implemented support for database query logging when the query fails, we could implement that in performance tests, so that even when they query isn't successful, we can record that it was sent to the database.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Issue fork drupal-3444060

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

catch created an issue. See original summary.

longwave made their first commit to this issue’s fork.

longwave’s picture

Status: Active » Needs work

This is the same two failures as over in #3417066-65: Upgrade PHPUnit to 10, drop Symfony PHPUnit-bridge dependency so if we can solve this we can sidestep that particular problem for now.

catch’s picture

Yes this looks great! We should just update the test coverage to match the extra things being recorded.

longwave’s picture

Status: Needs work » Needs review
catch’s picture

Status: Needs review » Reviewed & tested by the community
mondrake’s picture

Issue tags: +PHPUnit 10
alexpott’s picture

Version: 11.x-dev » 10.3.x-dev
Status: Reviewed & tested by the community » Fixed

Committed and pushed 970ff6e924 to 11.x and c333e1f5f4 to 10.3.x. Thanks!

  • alexpott committed c333e1f5 on 10.3.x
    Issue #3444060 by longwave, catch, mondrake: Implement failed database...

  • alexpott committed 970ff6e9 on 11.x
    Issue #3444060 by longwave, catch, mondrake: Implement failed database...

  • alexpott committed 970ff6e9 on 11.0.x
    Issue #3444060 by longwave, catch, mondrake: Implement failed database...

Status: Fixed » Closed (fixed)

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