Early data test case will fail randomly cause the anti-play protection from gnutls server

[xkqian]

Summary

We have one test case in tests/opt-testcases/tls13-misc.sh, it will fail randomly when the anti-replay protection is triggered by gnutls server.
It's one test case during development, and only test the early data indication writing in client hello, we should dig more about the gnutls server to find what cause the protection be triggered.

System information

Mbed TLS version (number or commit id): development
Operating system and version:
Configuration (if not default, please attach mbedtls_config.h):
Compiler and options (if you used a pre-built binary, please indicate how you obtained it):
Additional environment information:

Expected behavior

Test case passed

Actual behavior

Random failed.

Steps to reproduce

It's one random issue.
Please run the test case "TLS 1.3 m->G: EarlyData: basic check, good" in he file tests/opt-testcases/tls13-misc.sh.

[xkqian]

gnutls server failed here:

       /* It shouldn't be possible that the server's view of ticket
	 * age is smaller than the client's view.
	 */
	if (unlikely(server_ticket_age < client_ticket_age))
		return gnutls_assert_val(GNUTLS_E_ILLEGAL_PARAMETER);

We suspect that the time computation error or even the platform doesn't support time functions.

[xkqian]

The gnutls code path: https://www.gnupg.org/ftp/gcrypt/gnutls/v3.7/gnutls-3.7.2.tar.xz or https://gitlab.com/gnutls/gnutls/-/blob/master/lib/tls13/anti_replay.c#L151. And the error report happend in line 151 of file lib/tls13/anti_replay.c

[yuhaoth]

The line https://gitlab.com/gnutls/gnutls/-/blob/master/lib/tls13/anti_replay.c#L151 is not changed about 3years. I think it is most likely our fault.

[tom-cosgrove-arm]

Re-opening as it's not fully fixed, and we have #6788 to fix it