To be fully honest, this may not be a OSX (alone) condition, but may be a situation that only happens with OSX on Travis-CI, were resources are quite limited.
I have personal experience with tests that exercise parallelism or depend on timing to fail on Travis. Because I'm not 100% certain that this is a situation that only happens with OSX on Travis-CI, and because I'm not certain that we should be skipping tests because they're running on Travis-CI, let's disable them on OSX as a whole. A small note: this type of change makes me believe that there should be a list of testing related caveats or TODO list tracked on the documentation. Signed-off-by: Cleber Rosa <cr...@redhat.com> --- tests/Makefile.include | 3 +++ 1 file changed, 3 insertions(+) diff --git a/tests/Makefile.include b/tests/Makefile.include index 074eece558..c821b01467 100644 --- a/tests/Makefile.include +++ b/tests/Makefile.include @@ -87,7 +87,10 @@ check-unit-y += tests/test-rcu-simpleq$(EXESUF) check-unit-y += tests/test-rcu-tailq$(EXESUF) check-unit-y += tests/test-qdist$(EXESUF) check-unit-y += tests/test-qht$(EXESUF) +# test-qht-par gets stuck quite often on OSX +ifneq ($(CONFIG_DARWIN),y) check-unit-y += tests/test-qht-par$(EXESUF) +endif check-unit-y += tests/test-bitops$(EXESUF) check-unit-y += tests/test-bitcnt$(EXESUF) check-unit-y += tests/test-qdev-global-props$(EXESUF) -- 2.19.1
