Extend test suite to test different configurations

[adammoody]

As we start to have configuration parameters that enable/disable capabilities or new optimizations, we should be sure our test suite runs through all combinations. Note that this is complicated in that some test cases may no longer work, or the expected behavior may change.

For example, we may have a configuration option that changes whether stat() returns 0, local size, or the current global size pre-lamination. The test cases that check file size with stat will need to know this and know to check the correct expected value under each configuration.

• Test with shared memory only, no spill over

• Test with spill over only, no shared memory storage

• Test with both shared memory and spillover, with data sizes to utilize both

• Test with and without client write flattening

• Test with and without client reads via local extents

• Test with and without server reads via local extents

[adammoody]

@CamStan , @tonyhutter , got an issue started here we can use to discuss this.

[MichaelBrim]

We need to test I/O shuffle (i.e., read different data than written by the local rank) with data integrity checking turned on. For the writeread example, the relevant options are -x -k.

[CamStan]

Test the various ways of configuring UnifyFS to make sure they all work:

• envars
• config file
• command line options