From e467eef58d56421b06363ca98fbafa88164d72fb Mon Sep 17 00:00:00 2001 From: Nadav Har'El Date: Tue, 4 Jul 2017 13:31:28 +0300 Subject: [PATCH] Fix test to use non-wrapping range The test put a wrapping range into a non-wrapping range variable. This was harmless at the time this test was written, but newer code may not be as forgiving so better use a non-wrapping range as intended. Signed-off-by: Nadav Har'El Message-Id: <20170704103128.29689-1-nyh@scylladb.com> (cherry picked from commit d95f9085863a5223c6d07038ce10ce3af7cd04af) --- tests/partitioner_test.cc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tests/partitioner_test.cc b/tests/partitioner_test.cc index 5d8e86b1e5..249c3623bb 100644 --- a/tests/partitioner_test.cc +++ b/tests/partitioner_test.cc @@ -925,8 +925,8 @@ BOOST_AUTO_TEST_CASE(test_split_range_single_shard) { // tests for range_split() utility function in repair/range_split.hh static int test_split(int N, int K) { - auto t1 = token_from_long(0x6000'0000'0000'0000); - auto t2 = token_from_long(0x9000'0000'0000'0000); + auto t1 = token_from_long(0x2000'0000'0000'0000); + auto t2 = token_from_long(0x5000'0000'0000'0000); dht::token_range r{range_bound(t1), range_bound(t2)}; auto splitter = range_splitter(r, N, K); int c = 0;