The log file from a Chronicle-Queue build on Windows contains FileSystemException stack traces indicating that some Chronicle files could not be deleted because they were in use. This does not prevent the build from completing successfully (each test creates a new temporary directory); however, this can affect a Windows build server (abandoned files quickly use up space on the temporary file system). It does not affect Linux/Unix machines because those systems allow deleting files that are still open.
This is the same issue as OpenHFT#560, which was reported in the upstream project.