RTC test: fix __result variable

[0xc0170]

Result was not defined, thus causing attribute error

AttributeError: 'RTC_time_calc_test' object has no attribute '_RTC_time_calc_test__result'

@mprse @maciejbocianski please review

[0xc0170]

/morph build

[mbed-ci]

Build : SUCCESS

Build number : 801
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5784/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build

[mbed-ci]

Exporter Build : SUCCESS

Build number : 455
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/5784/

[fkjagodzinski]

Although this will fix an AttributeError, it introduces further confusion. It's unnecessary to override result() method in RTC_time_calc_test class in the first place (the device side decides if the test suite passed or not). I suggest removing result() and teardown() methods from this class altogether.

mbed-os/TESTS/host_tests/rtc_calc_auto.py

Lines 134 to 138 in c832515

	def result(self):
	return self.__result
	def teardown(self):
	pass

This way the code gets more readable.

[0xc0170]

Was not sure what was the intention with having result method. I'll remove it, as soon as test is finished

[0xc0170]

fixed

[fkjagodzinski]

Side note:
From what I've seen this result() method gets called if DUT does not send {{end;success}} / {{end;failure}} which may happen e.g. on test suite timeout.

https://github.com/ARMmbed/htrun/blob/9648fd73930cfa86967833e85a0f2ef5efaf9cd5/mbed_host_tests/host_tests_runner/host_test_default.py#L467-L473

[0xc0170]

Looks correct, we are getting timeouts today, so that might needs patching as well

[0xc0170]

/morph build

[mbed-ci]

Build : FAILURE

Build number : 802
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5784/

[0xc0170]

/morph build

[mbed-ci]

Build : FAILURE

Build number : 803
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5784/

[0xc0170]

@studavekar @kegilbert Can you please investigate the build failure? From the logs, blinky example passes, but tls example cant be fetched (OSError), that leads to all these failures

[0xc0170]

/morph build

[mbed-ci]

Build : FAILURE

Build number : 804
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5784/

[0xc0170]

webpage mbed os problems, that are operational now. restarting

/morph build

[mbed-ci]

Build : SUCCESS

Build number : 805
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5784/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build

[studavekar]

/morph test

[mbed-ci]

Exporter Build : SUCCESS

Build number : 456
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/5784/

[mbed-ci]

Test : SUCCESS

Build number : 637
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/5784/637

[adbridge]

This file was only introduced in a PR which is scheduled for 5.8, thus this also needs to go to 5.8.