I think that I’ll ignore this test failure
This really sucks, because of this:
This is part of the RavenDB release process, where we are actually hammering RavenDB and seeing if it breaks. And it usually takes about 24 hours to do a complete run.
This really sucks, because of this:
This is part of the RavenDB release process, where we are actually hammering RavenDB and seeing if it breaks. And it usually takes about 24 hours to do a complete run.
Comments
I thought you swopped Esent for Munin?
One could start with a test to see if the machine(s) on which the tests are ran have enough diskspace left, so that if this error occurs again, it'll crash fast....
@Neil Munin isn't recommended for Production. It's mostly there to allow in-memory integration testing and support for non Win32 platforms (where Esent doesn't run)