For a committed transaction, its durable timestamp should always be greater than or equal to its commit timestamp:

+                       WT_ASSERT(session,
+                           (prepare_state == WT_PREPARE_INPROGRESS ||
+                           durable_timestamp >= las_timestamp));

This assertion fails in test_schema_abort with the following state of the involved parameters:

(gdb) p prepare_state
$1 = 3 '\003' (WT_PREPARE_RESOLVED)
(gdb) p durable_timestamp
$2 = 46426
(gdb) p las_timestamp
$3 = 46428

Since test_schema_abort does not explicitly set the durable timestamp, its durable timestamp should not have diverged from the commit timestamp. Identify the cause of this divergence and then enable the assertion.