On 17/05/17 00:40, Chris Johns wrote:
On 16/05/2017 18:35, Sebastian Huber wrote:
On 16/05/17 10:28, Chris Johns wrote:
What we do need to do is make sure the test results express the true
state. If a test is broken it should fail. If it is tagged an
expected-fail we do not consider it a regression.
Loosing test coverage simply because a test uses a non-SMP feature
somehow is not really great.
I am sorry you have lost me. If the test is for something not
available when SMP is enabled why build it? This can be handled in the
build system. If the test is using something not available on SMP and
it can be written to work on SMP by not using that feature then the
test is broken on SMP and I would expect a fail until it is fixed.
Yes, some tests are broken on SMP with the SMP mode enabled, but not the
features they are testing. If you disable the tests, then you don't test
these features at all in SMP configurations.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
