Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Fix Travis CI failure of multiple_merges_during_fold_test #74

Merged
merged 3 commits into from Mar 5, 2013

Conversation

Projects
None yet
2 participants
Contributor

jtuple commented Dec 3, 2012

The environment that Travis runs test under unfortunately does not immediately pick up the expected number of files to merge for the different merge operations in the multiple_merges_during_fold_test. This commit changes the test to re-try merging until the expected result is seen (or eventually have the test timeout).

Fix Travis CI failure of multiple_merges_during_fold_test
The environment that Travis runs test under unfortunately does not
immediately pick up the expected number of files to merge for the
different merge operations in the multiple_merges_during_fold_test.
This commit changes the test to re-try merging until the expected
result is seen (or eventually have the test timeout).

@slfritchie slfritchie commented on an outdated diff Dec 4, 2012

src/bitcask.erl
-include_lib("eunit/include/eunit.hrl").
+-ifdef(TEST).
+%% -include_lib("eunit/include/eunit.hrl").
@slfritchie

slfritchie Dec 4, 2012

Contributor

Shouldn't the eunit.hrl header be -ifdef'ified and uncommented? This looks like a bit of debugging cruft.

slfritchie added a commit that referenced this pull request Mar 5, 2013

Merge pull request #74 from basho/jdb-fix-travis-failure
Fix Travis CI failure of multiple_merges_during_fold_test

After many intermittent timing failures over in TravisCI land, we have this:

    BUILD PASSED: [bitcask jdb-fix-travis-failure:771c92d] by Scott Lystig Fritchie https://travis-ci.org/basho/bitcask/builds/5266676

@slfritchie slfritchie merged commit 66d5cae into master Mar 5, 2013

1 check passed

default The Travis build passed
Details

@engelsanchez engelsanchez deleted the jdb-fix-travis-failure branch Mar 28, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment