Skip to main content

Crate store_io_conformance

Crate store_io_conformance 

Source
Expand description

§store-io-conformance

The checks every store-io platform backend must pass, on every file system it supports. A Suite runs each scenario in a fresh directory under a scratch root and returns a Report naming every scenario and what, if anything, went wrong; one failure never hides the others.

Two kinds of scenario:

  • The platform contract (the Platform and Queue traits): exclusive create and not-found mapping, sizes, many operations in flight completing once each with their buffers, durable writes and flushes, queue limits, read-only handles, rename and unlink, directory sync, the ownership lock, range state after a full write, release, and the probe’s honesty about what it could not read.
  • Store behaviour on that platform: a round trip through a reopen, a read-only open that changes nothing, ownership, and directory-mode replace.

The suite cannot cut power: crash behaviour is tested on the simulator (store-io-sim) and, for certification, on a power-cut rig.

Structs§

Outcome
One scenario’s outcome.
Report
The outcome of every scenario.
Suite
A conformance run over one platform and one scratch directory.