On 24.11.2016 12:06, Evgeny Kotkov wrote:
> Evgeny Kotkov <evgeny.kotkov_at_visualsvn.com> writes:
>>> The question is: what do we do about it? Complaining to Apple isn't
>>> likely to help. We could add a special case in the testcase for that
>>> version of SQLite on OSX, just to keep the test output in the green. But
>>> ... that seems like just a bit overdone.
>> To my mind, the test is of less concern, compared to the issue itself.
>> I would prefer to keep the test catching this bug for now, unless that
>> causes severe issues for maintainers. If that happens, we could add a
> Actually, let me rephrase myself.
> I think that we _should not_ change the test, because it does what it's
> supposed to do (catch bugs). In this case, maintainers would be better
> using official sqlite-amalgamation, until the bug in the customized SQLite
> library shipped with OS X is fixed. The failing test is a proper indication
> of this bug.
Ack. It's going to be painful if I ever update the OSX build slave, but
In the meantime, I've verified that, Homebrew's build does not use the
stock SQLite on the Mac but Homebrew's own version, which does not have
this problem. I don't know about Fink and other installers.
Received on 2016-11-24 13:23:51 CET