Snipping the test failure output from the build log so it does not get archived:

--- FAIL: TestJWT_ClaimsFromJWT_NotBeforeClaims (0.00s)
    --- FAIL: TestJWT_ClaimsFromJWT_NotBeforeClaims/static (0.01s)
        --- PASS: TestJWT_ClaimsFromJWT_NotBeforeClaims/static/custom_nbf_leeway_using_exp_with_no_clock_skew_leeway (0.02s)         --- PASS: TestJWT_ClaimsFromJWT_NotBeforeClaims/static/not_yet_valid_custom_nbf_leeway_using_exp_with_auto_clock_skew_leeway (0.02s)         --- PASS: TestJWT_ClaimsFromJWT_NotBeforeClaims/static/auto_nbf_leeway_using_exp_with_custom_clock_skew_leeway (0.02s)         --- PASS: TestJWT_ClaimsFromJWT_NotBeforeClaims/static/no_nbf_leeway_using_iat_with_auto_clock_skew_leeway (0.02s)         --- FAIL: TestJWT_ClaimsFromJWT_NotBeforeClaims/static/not_yet_valid_custom_nbf_leeway_using_exp_with_no_clock_skew_leeway_with_default_leeway (0.02s)         --- FAIL: TestJWT_ClaimsFromJWT_NotBeforeClaims/static/not_yet_valid_custom_nbf_leeway_using_exp_with_no_clock_skew_leeway (0.02s)         --- FAIL: TestJWT_ClaimsFromJWT_NotBeforeClaims/static/not_yet_valid_auto_nbf_leeway_using_exp_with_no_clock_skew_leeway (0.02s)

These look quite likely to be timing-sensitive tests, which are often a headache on Debian CI.

I have just uploaded consul 1.9.17+dfsg2-1 and as of now, it builds successfully on armel. That does not rule out the possibility however that these are intermittent test failures.

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to