From 462cffcd00c12e6c96d4c045572c0e76a2686538 Mon Sep 17 00:00:00 2001 From: Greg Hudson Date: Thu, 15 Jun 2017 11:59:18 -0400 Subject: Suppress y2038 GSS tests when time_t is 32-bit The GSSAPI time_t tests do not run correctly on 32-bit Solaris because time_t conversions are involved in the "kinit -l 8500d" step. Suppress the GSS y2038 tests when time_t is 32-bit. ticket: 8352 --- src/tests/gssapi/t_gssapi.py | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/src/tests/gssapi/t_gssapi.py b/src/tests/gssapi/t_gssapi.py index 98c8df2..6da5fce 100755 --- a/src/tests/gssapi/t_gssapi.py +++ b/src/tests/gssapi/t_gssapi.py @@ -185,10 +185,11 @@ realm.run(['./t_ciflags', 'p:' + realm.host_princ]) # contexts. realm.run(['./t_inq_ctx', 'user', password('user'), 'p:%s' % realm.host_princ]) +if runenv.sizeof_time_t <= 4: + skip_rest('y2038 GSSAPI tests', 'platform has 32-bit time_t') + # Test lifetime results, using a realm with a large maximum lifetime -# so that we can test ticket end dates after y2038. There are no -# time_t conversions involved, so we can run these tests on platforms -# with 32-bit time_t. +# so that we can test ticket end dates after y2038. realm.stop() conf = {'realms': {'$realm': {'max_life': '9000d'}}} realm = K5Realm(kdc_conf=conf, get_creds=False) -- cgit v1.1