We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The testcase "XTree<3> cancellation" consistently fails on my system.
Run ./ao/test/ao-test "XTree<3> cancellation"
./ao/test/ao-test "XTree<3> cancellation"
Output:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ao-test is a Catch v1.1 b3 host application. Run with -? for options ------------------------------------------------------------------------------- XTree<3> cancellation ------------------------------------------------------------------------------- /home/nick/ao/ao/test/xtree.cpp:212 ............................................................................... /home/nick/ao/ao/test/xtree.cpp:237: FAILED: REQUIRE( elapsed_ms.count() < 50 ) with expansion: 79 < 50 =============================================================================== test cases: 1 | 1 failed assertions: 1 | 1 failed
(The number of milliseconds it takes varies from 55 to 80.)
If cancel.store(true); is commented out, the computation takes 433816 milliseconds.
cancel.store(true);
None known.
The text was updated successfully, but these errors were encountered:
More conservative timeout (closes issue #66)
8d5f789
Okay, I've bumped that timeout a little bit, given the range that you found.
Sorry, something went wrong.
No branches or pull requests
The testcase "XTree<3> cancellation" consistently fails on my system.
Reproduction
Run
./ao/test/ao-test "XTree<3> cancellation"
Output:
(The number of milliseconds it takes varies from 55 to 80.)
Removing cancel
If
cancel.store(true);
is commented out, the computation takes 433816 milliseconds.End user visible impact
None known.
The text was updated successfully, but these errors were encountered: