Eric Niebler wrote:
I spent some time combing through the results, but found that a time-consuming way to find these sorts of bugs. I have to look at every test result for every library, making sure I'm comparing the right rows. Is there an easier way?
I'm not complaining, though. It's worth it, and I greatly appreciate having these test results.
I searched the test logs (without BOOST_RESULT_OF_USE_TR1) that contain `compile result="fail"` and `result_of` (plus some filters) using Ruby. Here is a list of matched results (20 items): libs/functional/forward/test/forward_adapter.test libs/functional/forward/test/lightweight_forward_adapter.test libs/fusion/test/invoke.test libs/phoenix/test/bind_not_test.test libs/phoenix/test/bind_rv_sp_test.test libs/phoenix/test/bind_stateful_test.test libs/phoenix/test/bind_test.test libs/phoenix/test/bug3289.test libs/phoenix/test/dynamic_tests.test libs/phoenix/test/exceptions.test libs/phoenix/test/if_tests.test libs/phoenix/test/lambda_tests.test libs/phoenix/test/loops_tests.test libs/phoenix/test/member.test libs/phoenix/test/new_delete_tests.test libs/phoenix/test/switch_tests.test libs/spirit/repository/test/qi_repo_advance.test libs/spirit/repository/test/qi_repo_keywords.test libs/spirit/test/lex_regression_file_iterator3-p3.test libs/utility/test/result_of_test.test Please enjoy it :-) Regards, Michel