tree 8f791ff029f1997582a31fbe4b8aff44944e3308
parent 61edde52a020cf052efb0480a09e2347bc1b6ecd
author Alastair Donaldson <afdx@google.com> 1568969006 +0100
committer GitHub <noreply@github.com> 1568969006 +0100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJdhJEuCRBK7hj4Ov3rIwAAdHIIAFoAw4jT+X8BuzMpl/SnOUPk
 G+MmPv7Ax2yrTKv0hgay5/FMXk7tEAJb3/mQRPCJLKu8duDK1eoKK334UJjqPjFT
 6OT2XZ/SiPHBFswzWl1is0LBD0HoNJ8L6q3UUgNdn9wJ0MFjAyvdCGjJt2Y5bBlw
 KxtQgZ0ELtSPl2VkZJcU8xyAHoE9YwtHCwyAZIQ9gkM9+JaA59na5iY764+MOETv
 ++h0CbKTQkd3+f8Sw95HuA3JUxjNc2Wz+jc7tLb4lMw/gk0xiKA318p78x0CHXGE
 fmOrd/V5VVU8Wkrj7oJdn3+mV7wwGkF96xosMcq99yGlbYI5YMQnyFqCHKPzZMU=
 =S6n8
 -----END PGP SIGNATURE-----
 

Disable long-running fuzzer tests by default (#2887)

spirv-fuzz has useful tests that run the fuzzer and shrinker, to give
the whole tool a good shake up, effectively "fuzzing the fuzzer".  The
problems that this detects are sensitive to the source of randomness
that is used, which can change from test platform to test platform.
It is thus not a good idea to run these tests by default during
continuous integration - they may end up failing due to environtal
factors, making it look like an unrelated change has broken the fuzzer
when really the fuzzer has revealed an already-existing bug in itself.

This change makes the tests disabled by default; they can enabled
during dedicated testing of the fuzzer.