From 982685d3a06affc1f5bf717d821e2ab84f32f1a2 Mon Sep 17 00:00:00 2001 From: Daniel James Date: Wed, 5 Oct 2016 00:57:58 +0100 Subject: [PATCH] Adjust order of variables to see if intel failure changes. So currently on one intel tester find_tests is failing the 'pos != x.end()' test, but not the 'const_pos != x_const.end()' test for unordered_set (and possibly others, the test results are truncated). I'm a bit stumped as to why this should be, as for unordered_set the const and non-const versions are basically the exact same code. See if changing the order makes any difference to what fails. --- test/unordered/find_tests.cpp | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/test/unordered/find_tests.cpp b/test/unordered/find_tests.cpp index 45151e99..5bb1b7c0 100644 --- a/test/unordered/find_tests.cpp +++ b/test/unordered/find_tests.cpp @@ -37,15 +37,15 @@ void find_tests1(X*, test::random_generator generator) tracker.begin(); it1 != tracker.end(); ++it1) { BOOST_DEDUCED_TYPENAME X::key_type key = test::get_key(*it1); - 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))); + iterator pos = x.find(key); BOOST_TEST(const_pos != x_const.end()); BOOST_TEST(const_pos != x_const.end() && x_const.key_eq()(key, test::get_key(*const_pos))); + BOOST_TEST(pos != x.end()); + BOOST_TEST(pos != x.end() && + x.key_eq()(key, test::get_key(*pos))); BOOST_TEST(x.count(key) == tracker.count(key));