More details:
1. Tests don't check if the timeout has been hit, so they do not
report failures properly. By looking at Jenkins it's clear, that
the timeout issue is happening in most cases.
2. The tests fail randomly from time to time, if the test's callback
is called, so the timeout is NOT hit and the tests are actually
doing their job, indicating that something works incorrectly.
This change is ment to prevent other developers from being
disturbed by the random test failures, which should be eventually
fixed in IOT-1807.
Change-Id: Ibe25cd2adc74ec0676719a1ec506977c35ec20ce
Signed-off-by: Pawel Winogrodzki <pawelwi@microsoft.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/17327
Tested-by: jenkins-iotivity <jenkins@iotivity.org>
Reviewed-by: Dan Mihai <Daniel.Mihai@microsoft.com>
return OC_STACK_DELETE_TRANSACTION;
}
-TEST_F(OCDiscoverTests, DiscoverResourceWithValidQueries)
+// Disabled to unblock other developers untill IOT-1807 is done.
+TEST_F(OCDiscoverTests, DISABLED_DiscoverResourceWithValidQueries)
{
itst::DeadmanTimer killSwitch(LONG_TEST_TIMEOUT);
discoverRTCB.Wait(100);
}
-TEST_F(OCDiscoverTests, DiscoverResourceWithInvalidQueries)
+// Disabled to unblock other developers untill IOT-1807 is done.
+TEST_F(OCDiscoverTests, DISABLED_DiscoverResourceWithInvalidQueries)
{
itst::DeadmanTimer killSwitch(LONG_TEST_TIMEOUT);