Open fgalan opened 10 years ago
On recovering the recover_ontimeinterval_threads we should include the multitenant case (basically, populate 2 tenants database and check that the subscriton in each one are recovered correctly).
Given that new tests has been .DISABLED (e.g. existTest.DISABLED), I have changed the name of the issue to make it extensible to other.
At the present moment the disabled test are:
fermin@neodeb:~/src/fiware-orion/test$ find functionalTest/ | grep DISABLED
functionalTest/cases/0000_ipv6_support/ipv4_only.test.DISABLED
functionalTest/cases/0000_ipv6_support/ipv6_only.test.DISABLED
functionalTest/cases/2207_not_spurious_decimals_in_custom_notifications/not_spurious_decimals_in_custom_notifications.test.DISABLED
functionalTest/cases/1156_qfilters_and_compounds/qfilters_and_compounds_equals_null.test.DISABLED
functionalTest/cases/1310_suspect_200OK/suspect_200OK.test.DISABLED
functionalTest/cases/0000_bad_requests/exit.test.DISABLED
functionalTest/cases/0917_queryContext_behaves_differently/query_with_and_without_forwarding.test.DISABLED
This test [recover_ontimeinterval_recover.test ] has a long tradition of problems in the harness test suite and now it seems that also produces hangs in Ubuntu (and sometimes in Debian) in the valgrind test suite.
We have renamed this file to
recover_ontimeinterval_threads.DISABLED
to disable it. After fixing it and closing this issue, we will named it back to.test
.Effort: 3 man day