The JavaChronicle was incorrectly reporting the availability of a next index on the Linux-based CI servers. This condition was not happening on the Mac OS X JDK. Not sure why that would work differently but I added some code to capture errors and log them at DEBUG level but assume that an inability to read data from the Chronicle is mistake of the system and thus will return null to the user rather than throwing an exception.