From 2be69b3eb91898a6910eb68d10b64a83dc77da04 Mon Sep 17 00:00:00 2001 From: Daniel James Date: Wed, 27 Jul 2016 06:51:05 +0100 Subject: [PATCH] A little more information in the find_tests. Now the intel-linux tester that was failing for erase_tests is passing, but has started failing for find_tests instead. Oddly the test for non-const find is failing, but the const find is fine - this doesn't make much sense as they should be the same. Not sure, but it suggests the problem might be in the way iterators are handled, rather than the data structure? Checking the iterators before checking that the keys are equal in order to tell which part of the test is failing. --- test/unordered/find_tests.cpp | 2 ++ 1 file changed, 2 insertions(+) diff --git a/test/unordered/find_tests.cpp b/test/unordered/find_tests.cpp index a310d40c..45151e99 100644 --- a/test/unordered/find_tests.cpp +++ b/test/unordered/find_tests.cpp @@ -40,8 +40,10 @@ void find_tests1(X*, test::random_generator generator) iterator pos = x.find(key); BOOST_DEDUCED_TYPENAME X::const_iterator const_pos = x_const.find(key); + BOOST_TEST(pos != x.end()); BOOST_TEST(pos != x.end() && x.key_eq()(key, test::get_key(*pos))); + BOOST_TEST(const_pos != x_const.end()); BOOST_TEST(const_pos != x_const.end() && x_const.key_eq()(key, test::get_key(*const_pos)));