tree 6282cfffc7cab400098ef061109ea23c9b6e6e6b
parent 0cdfdb3ecb20fbff11e401c34143fe0e8ff61f83
author David Grove <dgrove-oss@users.noreply.github.com> 1625602628 -0400
committer GitHub <noreply@github.com> 1625602628 -0400
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJg5LpECRBK7hj4Ov3rIwAAWLIIAFwedn6UOMDd0fNdahk2zq3c
 HUwOzj00I/IjOdkhLbXoSwrKprF47ASZzBevIRrTKcymKVKBaTUE0nfWInAR56/o
 /9cPXv0VpWeqjM9/ILLAlisORC3aZl1bPRTd+ug4sOqfmaIWkYofPZ1MeHHMUSVI
 GjKgF8KcBnILGrfMoHBj/RMVNIeBmv8o/rjAelqL0k4JV7dD4J/Bv394XdSv6ycN
 R3Olsdy/4mqwv9aMk0PP4tGfewiCcyM66tQZuDN1HnGYiSAkKU5C1mqY94/Mopu8
 3RqyWM2PuHozVk3/KrSS+Sig044xGEEO8s2hUf7rB3LciSmxuDrzlF3aj0ElykU=
 =k/mR
 -----END PGP SIGNATURE-----
 

Disable StandaloneKCFTests (#5140)

The only test case being run (invoke a blocking action
and get a result) fails quite frequently when run in
a travis-ci environment.  It appears we usually hit the
60 second timeout and return a 202 with the activation id
instead of the expected result.  This is "ok", but the test
is not prepared to handle it.

An alternative would be to modify the test to also accept a 202
response and then poll until the result was available, but that
would take significantly more work.