Bug #3182
Updated by Tom Clegg over 10 years ago
Example from https://ci.curoverse.com/job/arvados-api-server/593/console:
<pre>
1) Failure:
UsersTest#test_setup_the_active_user [/var/lib/jenkins/workspace/arvados-api-server/apps/workbench/test/integration/users_test.rb:146]:
Failed assertion, no message given.
95 runs, 279 assertions, 1 failures, 0 errors, 0 skips
Coverage report generated for Unknown Test Framework to /var/lib/jenkins/workspace/arvados-api-server/apps/workbench/coverage. 11695 / 26889 LOC (43.49%) covered.
Coverage report Rcov style generated for Unknown Test Framework to /var/lib/jenkins/workspace/arvados-api-server/apps/workbench/coverage/rcov
********** !!!!!! WORKBENCH TESTS FAILED !!!!!! **********
</pre>
Identify race conditions in the test and, if possible, implement synchronizations to ensure they do not result in bogus failures.
Another example, from https://ci.curoverse.com/job/arvados-api-server/657/console
<pre>
1) Failure:
UsersTest#test_create_a_new_user [/var/lib/jenkins/workspace/arvados-api-server/apps/workbench/test/integration/users_test.rb:64]:
Failed assertion, no message given.
</pre>