Cameron Stanavige

read, readv, pread, pread64, fread We might want to come up with a test that opens two distinct file descriptors to the same file, e.g., for reading at different points...

If possible, could you do be a quick favor and try this again with any version 8 of gcc and see if it still fails? We've seen an issue before...

Alternatively, this has brought up the question again that we may no longer need FlatCC as a dependency (#550). So we may just remove this sooner rather than later.

A couple updates/things to try to see if we can figure out what's happening: 1. Try installing with our dev branch; `spack install unifyfs@develop`. We've made a lot of changes...

Adding a reference to #511 for quick access to where this work was done. Also noting that this test was changed to use the `test_might_fail` directive to essentially label it...

Examples that need to laminate a file ([size.c](https://github.com/LLNL/UnifyFS/blob/dev/examples/src/size.c), [write.c](https://github.com/LLNL/UnifyFS/blob/dev/examples/src/write.c)) currently do so by using `chmod` to remove the write bits (#354). These will need to be updated once there is...

I agree that we should remove the `test_might_fail`. Go ahead with that PR as it would be good to know if this is failing on Travis. However, @jenest is also...

I agree. This process is probably not necessary as it might overcomplicate the process of adding one wrapper. A script like this could serve as a nice check though that...

Yes, the CI tests current default is to execute on 4 nodes with 2 processes-per-node and the most recent `dev` branch is passing. That said, the CI suite is currently...

@MichaelBrim, does #284 with your implementation of https://github.com/LLNL/UnifyCR/blob/984472b5a58f13f8b4008f5e7bb15b0e20b22547/examples/src/Makefile.am#L45 https://github.com/LLNL/UnifyCR/blob/984472b5a58f13f8b4008f5e7bb15b0e20b22547/examples/src/testutil.h#L38-L40 resolve this? Or do other examples still need to be converted to this in order to be resolved?