On 22/05/17 17:29, Eric Anholt wrote:
Jose Fonseca writes:
I suppose the failures happen with S2TC lib-dxtn implementation.
Because I haven't seen them failing with the old implementation, or when
no implementation is present (as the tests will just skip.)
We could craft
Jose Fonseca writes:
> I suppose the failures happen with S2TC lib-dxtn implementation.
> Because I haven't seen them failing with the old implementation, or when
> no implementation is present (as the tests will just skip.)
>
> We could craft the test cases so they aren't
Rhys Kidd writes:
> On 21 May 2017 at 19:33, Roland Scheidegger wrote:
>
>> I suppose the s3tc problems should go away rather sooner than later, but
>> isn't it possible to just disable the formats tests?
>>
>
> Yes, see USE_TXC_DXTN that was introduced
I suppose the failures happen with S2TC lib-dxtn implementation.
Because I haven't seen them failing with the old implementation, or when
no implementation is present (as the tests will just skip.)
We could craft the test cases so they aren't sensitive to S2TC. On the
other hand the patent
On 21 May 2017 at 19:33, Roland Scheidegger wrote:
> I suppose the s3tc problems should go away rather sooner than later, but
> isn't it possible to just disable the formats tests?
>
Yes, see USE_TXC_DXTN that was introduced in
29322daef2b77c4d869d2945fa1226e6b433c68
to
I suppose the s3tc problems should go away rather sooner than later, but
isn't it possible to just disable the formats tests?
Roland
Am 18.05.2017 um 23:27 schrieb Eric Anholt:
> Every push a developer does to a travis-enabled github comes back as fail,
> because the unit tests are already
Every push a developer does to a travis-enabled github comes back as fail,
because the unit tests are already failing:
Testing util_format_dxt5_rgba_pack_rgba_float ...
FAILED: 40 bd 48 90 20 01 12 20 53 76 ab 32 00 10 15 50 obtained
f8 11 c5 0c 9a 73 b4 9c f6 8f ab 32 2a 9a