foundationdb/tests/AsyncFileMix.txt
Alex Miller 17570b5b10 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 02:03:30 -07:00

17 lines
337 B
Plaintext

testTitle=AsyncFileReadWriteTest (Uncached)
useDB=false
runSetup=true
clearAfterTest=false
testName=AsyncFileRead
testDuration=10.0
numParallelReads=1000
readSize=4096
unbufferedIO=true
uncachedIO=true
fileName=aftest.bin
fileSize=10000000
sequential=false
unbatched=true
writeFraction=0.999