foundationdb/tests/AsyncFileWrite.txt

testTitle=AsyncFileWriteTest
runSetup=true
clearAfterTest=false
useDB=false

    testName=AsyncFileWrite
    testDuration=10.0
    numParallelWrites=200
    writeSize=16384
    ;fileName=/home/ajb/testfile
    fileSize=10002432
    unbufferedIO=true
    sequential=false
Initial repository commit 2017-05-26 04:48:44 +08:00			`testTitle=AsyncFileWriteTest`
			`runSetup=true`
			`clearAfterTest=false`
			`useDB=false`
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=AsyncFileWrite`
			`testDuration=10.0`
			`numParallelWrites=200`
			`writeSize=16384`
			`;fileName=/home/ajb/testfile`
			`fileSize=10002432`
			`unbufferedIO=true`
			`sequential=false`