{"push_id":766528679,"size":1,"distinct_size":1,"ref":"refs/heads/filestream_async_buffering","head":"76696780ad8f639198f2f8d0706ce57cc172c394","before":"9fa7f331873591df8038c4cf4ca64502a10ddc94","commits":[{"sha":"76696780ad8f639198f2f8d0706ce57cc172c394","author":{"email":"94274d0b635748ad8df96c0fc4f19e1ecd3f67e2@microsoft.com","name":"stephentoub"},"message":"Add more tests for FileStream\n\n- Mainly, I added several tests (with lots of theory-based parameterized inputs) to stress WriteAsync: many concurrent writes, long chains of writes, etc., for various size inputs and buffers, async vs not, etc.\n- There were multiple variations on Flush tests based on whether to use Flush(), Flush(false), or False(true).  I combined these all into single theories.\n- I then added some more Flush tests for some missing cases highlighted by code coverage, e.g. flushing reads.\n- I then duplicated these tests for FlushAsync, and added some additional tests specific to FlushAsync, e.g. cancellation.\n- I added a few tests for pipes.","distinct":true,"url":"https://api.github.com/repos/stephentoub/corefx/commits/76696780ad8f639198f2f8d0706ce57cc172c394"}]}