1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
name: Durability
# Split into its own workflow so it carries its own status badge. A
# badge is per workflow, not per job, so a suite whose result the README
# advertises has to be a workflow of its own.
on:
push:
branches:
pull_request:
workflow_dispatch:
env:
CARGO_TERM_COLOR: always
# The profile written for CI: a slower, noisier host gets a looser
# slow-timeout than a workstation, and one retry so a genuinely flaky
# test is reported as flaky rather than as a failure. See
# `.config/nextest.toml`.
NEXTEST_PROFILE: ci
RUSTFLAGS: -D warnings
# Every `run` step goes through `bash -eo pipefail` rather than
# GitHub's default `bash -e`. Without `pipefail` a step like
# `just cov-summary | tee summary.txt` reports `tee`'s exit status,
# so a recipe that died with "command not found" still concluded
# green and published an empty report.
defaults:
run:
shell: bash
jobs:
# Durability, split out from `test` because it fails for different
# reasons and is worth reading on its own: crash recovery, power loss,
# the fault shim, the lifecycle sweep and the MVCC invariants.
durability:
runs-on: ubuntu-latest
timeout-minutes: 25
steps:
- uses: actions/checkout@v4
- uses: extractions/setup-just@v2
- uses: dtolnay/rust-toolchain@stable
- uses: Swatinem/rust-cache@v2
- uses: taiki-e/install-action@nextest
- name: Crash recovery
run: just test-crash
- name: Power loss
run: just test-power
- name: Fault injection smoke
run: just test-fault
- name: Lifecycle
run: just test-lifecycle
- name: MVCC invariants
run: just mvcc
# The exhaustive halves of the same families. Every truncation offset
# and every bit flip is a large cross product, so these run nightly
# rather than on every PR.
# The exhaustive halves of the same families. Every truncation offset
# and every bit flip is a large cross product, so these run nightly
# rather than on every PR.
durability-exhaustive:
runs-on: ubuntu-latest
timeout-minutes: 60
steps:
- uses: actions/checkout@v4
- uses: extractions/setup-just@v2
- uses: dtolnay/rust-toolchain@stable
- uses: Swatinem/rust-cache@v2
- uses: taiki-e/install-action@nextest
- name: Exhaustive corruption sweep
run: just test-corruption-slow
- name: Model-based durability proptest
run: just test-durability-slow
- name: Resource limits
run: just test-extremes
# Browser wasm. `wasm-wasip1` above covers the wasi target, which has a
# real `std::fs`; this covers `wasm32-unknown-unknown`, which has no
# filesystem at all and reaches storage through OPFS. OPFS's
# `createSyncAccessHandle` only exists inside a Web Worker, so there is
# no way to exercise it without a real browser.