On 9 November 2018 at 15:30, Cleber Rosa <cr...@redhat.com> 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.
Does this test still get stuck in builds after a458774ad711bceabefb ? That fixed an OSX-specific problem that caused hangs (notably in test-bdrv-drain, but it could I guess also affect other tests). thanks -- PMM
