Configuration of directories for IO

[lucaparisi91]

The paths of the filesystem are currently configured in each test doing I/O. At the moment, they all write to a shared z19 directory on each of the archer2 filesystem. That means the tests will break when run from another project account or when run on a machine with different file systems , such as on the TDS.

It would be good for the base directories to be configured at run time. One would add an option to the reframe command or modify a config file and all the tests would perform output within those directories.

[aturner-epcc]

Maybe a better approach would be to have a test that tests which file systems and directories you can write to. The IO tests would then be dependent on this test completing successfully and take the settings from that successful test.

[aturner-epcc]

Example of how to do what we need at:

https://reframe-hpc.readthedocs.io/en/stable/tutorial_deps.html#depending-on-parameterized-tests

[glumr]

If it was my choice I would have a way to tell reframe which 'temporary' locations can be used for filesystem tests. This is something that it is very useful for anyone unfamiliar with a test suite to be aware of, not least because you would want to check no huge files or crazily fillied directories still exist on completion. Even getting this right across projects on the same machine is going to be a pain.

[JPRichings]

@lucaparisi91 can this be closed now?

[lucaparisi91]

@lucaparisi91 can this be closed now?

I do not think has been addressed yet.