foundationdb/tests/DiskDurability.txt

testTitle=DiskDurability
useDB=false
timeout=360000

    testName=DiskDurability
    pagesPerWrite=1
    writers=64
    fileName=deleteme
    filePages=1000000
    testDuration=360000
Merge branch 'fix-io-timeout-handling' # Conflicts: # fdbrpc/AsyncFileKAIO.actor.h # fdbrpc/sim2.actor.cpp # fdbserver/KeyValueStoreSQLite.actor.cpp # fdbserver/optimisttest.actor.cpp # fdbserver/worker.actor.cpp # fdbserver/workloads/MachineAttrition.actor.cpp # tests/fast/SidebandWithStatus.txt # tests/rare/LargeApiCorrectnessStatus.txt # tests/slow/DDBalanceAndRemoveStatus.txt 2017-05-27 08:43:28 +08:00			`testTitle=DiskDurability`
			`useDB=false`
			`timeout=360000`
Make the testspec more restrictive in terms of what can be set where. Testspec is currently very permissive in very misleading ways. In particular, the tester parser itself will swallow K=V settings and apply them at the test level, which breaks how a person would expect the scoping to work. Other settings apply to the entire simulation run globally, but appear to be workload specific. Even further, others affect simulation cluster creation or test harness behavior, but can again be set anywhere in a testspec. This changes testspec parsing to error if a setting that applies globally is anywhere but the top of the file, or if a setting that applies test-wide is applied to a workload instead of a test. 2020-07-06 17:03:30 +08:00
			`testName=DiskDurability`
			`pagesPerWrite=1`
			`writers=64`
			`fileName=deleteme`
			`filePages=1000000`
			`testDuration=360000`