limbo/simulator/runner
Jussi Saurio cc643362a4 sim: remove "run_once faults"
This kind of fault does not semantically represent anything real,
since we already have fault injection for every concrete IO operation
like reading, writing, syncing and so forth.

Moreover, having this feature is the direct cause of the false positive
simulator failure as reported in issue #2727. There, a "run_once fault"
happened immediately after we fsynced following an INSERT, which caused
the simulator to think the INSERT failed, and later a sim assertion failed
because the on-disk database had 1 more row than it thought it would.
2025-08-22 10:13:06 +03:00
..
bugbase.rs sim: use 'git rev-parse --show-toplevel' for getting base dir 2025-08-20 09:58:21 +03:00
cli.rs FaultyQuery enabled by default 2025-08-18 11:52:10 -03:00
clock.rs cli options for max and min tick + adjust github action to run with faster clock so no timeouts happen 2025-07-17 12:25:31 -03:00
differential.rs chore: fix clippy errors 2025-07-16 19:34:42 +01:00
doublecheck.rs
env.rs FaultyQuery enabled by default 2025-08-18 11:52:10 -03:00
execution.rs Property TableHasExpectedContent should just check the expected 2025-08-18 16:00:59 -03:00
file.rs add File path to SimulatorFile 2025-08-18 11:52:10 -03:00
io.rs sim: remove "run_once faults" 2025-08-22 10:13:06 +03:00
mod.rs modify clock to use simulated time instead 2025-07-17 12:24:43 -03:00
watch.rs Add --keep-files flag and force Drop of database in simulator to prevent issues with the Registry 2025-08-15 17:54:40 -04:00