On Fri, Nov 09, 2018 at 10:30:01 -0500, Cleber Rosa wrote: > 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>
Is there a way to know where it hangs? Also, are these the g_test_quick tests, or the other ones? It it's just a matter of the program taking too long to run, we could just reduce the length of the !quick tests (currently at 5s vs. 1s for the quick ones). Thanks, Emilio