On 2014-10-14 04:16 PM, Michael Stahl wrote:
On 14.10.2014 16:04, Tor Lillqvist wrote:
i wonder if there's a buggy OpenCL driver on that Mac that needs to be
blacklisted somewhere?
Somebody else was wondering the same earlier this week. But there isn't
such a large variety of OpenCL drivers (or whatever the correct term is)
on OS X. Either or code is sliughtly buggy, or there is a bug in Apple's
OpenCL implementation that manifests itself when the code happens to
execute on a specific OpenCL device (i.e. the CPU or a specific GPU).
But the OpenCL driver version number as seen by our code is the same in
all cases on a certain OS X version, I think. Not sure if we can
blacklist only based on OpenCL driver version, or also specific
driver+device combinations.
in any case, somebody needs to investigate *why* the test is failing for
some, as it may fail for end users too in some scenario then; just
disabling it on Mac is not the best strategy :)
It doesn't fail reliably, and it only seems to happen under high load.
Anyhow, it's been failing for months and no-one has stepped up, so I commented it out so I can stop
ignoring the buildbots.
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.