In our internal build bot, we were seeing random test failures due to running out of disk space which we eventually traced back to this test which tries to create a large file to test with. This was being written to disk and eating most if not all of the 59GB of free space we had remaining on the machine. And while this test itself did not fail, it caused other tests running at the same time to fail due to being unable to write their output to the disk.
It was discovered that the test should still work with a smaller value which also avoids creating as large of a file. I've run the LLD tests with this change locally multiple times and it seems to avoid the problem we were encountering.