fold_visits_frozen_test(true) occasionally freezes on the builders

[evanmcc]

fold_visits_frozen_test with RollOver == true seems to freeze sometimes. I looked into this on a colo machine and my laptop but I suspect that maybe they're too fast. It shouldn't take more than ~2 seconds to run. We should get to the bottom of it before the RC.

======================== EUnit ========================
module 'bitcask'
  bitcask: a0_test...[0.100 s] ok
  bitcask: roundtrip_test...
=INFO REPORT==== 16-Apr-2014::19:43:58 ===
Bitcask IO mode is: bitcask_file
[0.505 s] ok
  bitcask: write_lock_perms_test...[0.266 s] ok
  bitcask: list_data_files_test...[0.024 s] ok
  bitcask: fold_test...[1.874 s] ok
  bitcask: iterator_test...[0.244 s] ok
  bitcask: fold_corrupt_file_test...
=ERROR REPORT==== 16-Apr-2014::19:44:02 ===
Trailing data, discarding (10 bytes)

=ERROR REPORT==== 16-Apr-2014::19:44:02 ===
Trailing data, discarding (14 bytes)
[0.550 s] ok
  bitcask:1687: fold_visits_frozen_test_...[2.301 s] ok
  bitcask:1688: fold_visits_frozen_test_...process killed by signal 11
program finished with exit code -1
elapsedTime=29.704782

[slfritchie]

bitcask:1688: fold_visits_frozen_test_...process killed by signal 11

Hrm, SIGSEGV. Really?

[evanmcc]

Used to be a timeout. I was seeing 11 and reading 15. Are cores on on the
builders?

[michellep-basho]

Bumped this out to 2.0.1 to keep an eye on it, but per Evan and Engel it has not come up again recently with pre2.0.

[jonmeredith]

@engelsanchez @slfritchie anybody seen this lately with all the recent work?

[engelsanchez]

Ah, it was bumped. During our one triage session my vote was for closing. We will re-open if seen again (it hasn't). I actually fixed something in one of our last PRs that quite likely had something to do with this problem: The test ran twice on the same directory, and I debugged it once and notice the next test would pick up the keydir from the previous run. Closing.