Changes between Version 2 and Version 9 of Ticket #37371


Ignore:
Timestamp:
Nov 5, 2026, 6:43:30 AM (3 days ago)
Author:
Sarah Boyce
Comment:

Thank you!

I've accepted the ticket with the suggested scope (and updated the title and description to reflect this) Feel free to open a separate ticket for cleaning up the parallel worker database files when the source database is in-memory and we'll triage it 👍

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #37371

    • Property Owner set to Becky Smith
    • Property Status new → assigned
    • Property Triage Stage Unreviewed → Accepted
    • Property Summary Inconsistent behaviour when running tests with `--keepdb` flag and sqlite backend → Misleading test database messages when using --keepdb with in-memory SQLite databases

  • Ticket #37371 – Description

    v2 v9  
    7575
    7676The fix for this will depend on how --keepdb is handled in the serial case. If we update the docs and logs to be more explicit about the fact that --keepdb will have no effect when there's no TEST db configured, then the parallel case should behave consistently and clean up its cloned dbs when there's no TEST db configured. If we modify the behaviour so that --keepdb uses an on-disk file that can be preserved, then I think the existing code will work as expected, although it would be worth documenting that running in parallel will use on-disk files, even if the TEST settings specify an in-memory file.
     77
     78------
     79
     80Following the discussion below, this ticket is limited to correcting the misleading log messages and documenting that `--keepdb` does not preserve in-memory SQLite test databases. This applies both to the default configuration and to an explicitly configured in-memory `TEST["NAME"]`. Database selection and preservation behaviour should remain unchanged.
Back to Top