Test failure on 32-bit: (actual_str == EXPECTED_NOT_VALID_AFTER): ("2037-12-31T23:23:23Z" == "2046-07-25T18:13:10Z")
The GNUTLS API for expiration dates is based on time_t
, which is 32-bit on most 32-bit architectures (newer ILP32 ABIs like x32 are a notable exception). In particular, i386 has 32-bit time_t
, and this is unlikely to change until the last possible moment, for compatibility with legacy 32-bit binaries.
This results in:
1..26
# Start of tls tests
# Start of gnutls tests
# Start of certificate tests
ok 1 /tls/gnutls/certificate/create-pem
ok 2 /tls/gnutls/certificate/create-der
ok 3 /tls/gnutls/certificate/create-with-key-pem
ok 4 /tls/gnutls/certificate/create-with-key-der
ok 5 /tls/gnutls/certificate/create-with-issuer
ok 6 /tls/gnutls/certificate/create-with-garbage-input
ok 7 /tls/gnutls/certificate/pkcs11
ok 8 /tls/gnutls/certificate/private-key
ok 9 /tls/gnutls/certificate/private-key-pkcs11
ok 10 /tls/gnutls/certificate/create-chain
ok 11 /tls/gnutls/certificate/create-no-chain
ok 12 /tls/gnutls/certificate/create-list
ok 13 /tls/gnutls/certificate/create-list-bad
ok 14 /tls/gnutls/certificate/verify-good
ok 15 /tls/gnutls/certificate/verify-bad-identity
ok 16 /tls/gnutls/certificate/verify-bad-ca
ok 17 /tls/gnutls/certificate/verify-bad-before
ok 18 /tls/gnutls/certificate/verify-bad-expired
ok 19 /tls/gnutls/certificate/verify-bad-combo
ok 20 /tls/gnutls/certificate/is-same
ok 21 /tls/gnutls/certificate/not-valid-before
Bail out! GLib-Net:ERROR:../tls/tests/certificate.c:689:test_certificate_not_valid_after: assertion failed (actual_str == EXPECTED_NOT_VALID_AFTER): ("2037-12-31T23:23:23Z" == "2046-07-25T18:13:10Z")
on e.g. Debian i386.
Merge request to follow.