Jose Fonseca <jfons...@vmware.com> 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 sensitive to S2TC. On the > other hand the patent expires this year IIRC, so probably not worth > spending time on it. > > Honestly, I'm happy skipping all s3tc unit tests until we have full s3tc > in Mesa mainline source tree.
I don't see s2tc in any logs or in the travis-ci, so I don't think it's installed. Do you have a suggestion for how to rip out the s3tc unit tests under scons? I'd really like to be able to push my code to github again without getting build errors thrown back at me.
signature.asc
Description: PGP signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
