#6965 (Database isn't virgin after pm ddt (double-dump test))

by Luc Saffre · in Developers · assigned to Luc Saffre

docs/projects/noi1e.rst runs "pm ddt" in the noi1e database, and sometimes this all remaining noi1e or noi1r doctests of the test suite to fail with

Database noi1e isn't virgin:

- memo.Mention: 13 rows deleted

Cannot restore database because some rows have been deleted

2 mois, 1 semaine ago by Luc Saffre about #6965 (Database isn't virgin after pm ddt (double-dump test)) : I now marked this "pm ddt" in noi1e.rst doctext as +SKIP.
2 mois, 1 semaine ago by Luc Saffre in reply to Luc Saffre about #6965 (Database isn't virgin after pm ddt (double-dump test)) : 'pm ddt' now calls dbhash.mark_virgin(), and the dbhash.json file gets written, but its content is unchanged, and the startup import in subsequent doctests continue to say that the database is not virgin and that 13 rows in memo.Mention have been deleted.
2 mois, 1 semaine ago by Luc Saffre about #6965 (Database isn't virgin after pm ddt (double-dump test)) (1 reply) : I'm still struggling with the failure "Database .../book/lino_book/projects/noi1e/settings isn't virgin: memo.Mention: 13 rows deleted"
2 mois, 1 semaine ago by Luc Saffre about #6965 (Database isn't virgin after pm ddt (double-dump test)) : I updated the ddt admin command to call dbhash.mark_virgin(), which somehow works around the problem. But I don't yet understand the reason of this effect.
2 mois, 1 semaine ago by Luc Saffre about #6965 (Database isn't virgin after pm ddt (double-dump test)) : Created new Ticket #6965 (Database isn't virgin after pm ddt (double-dump test)).