Refactor "Corrupt Data" Tests in TestHLogSplit
Review Request #1115 - Created Oct. 28, 2010 and submitted - Latest diff uploaded
So I took the approach taken with the instrumented sequence file rider. Not sure if exposing those methods in the WALReader is cool so I am down with other suggestions. - Add a FaultySequenceFileLogReader - Un-commented the 2935 tests
Running on our internal hudson as I type this. Also I ran the TestHLogSplit test locally. I'll update the review if hudson is green.