Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Future test error in OCSPTest.TestGoodOCSP #1889

Closed
greghogan opened this issue Sep 30, 2024 · 1 comment · Fixed by #1891
Closed

Future test error in OCSPTest.TestGoodOCSP #1889

greghogan opened this issue Sep 30, 2024 · 1 comment · Fixed by #1891

Comments

@greghogan
Copy link

Problem:

When setting the system time into the future (+10 years in my case) the OCSPTest.TestGoodOCSP test breaks with the errors read out-of-order.

Relevant details

AWS-LC version: 1.36.0 and 1.34.2

System information:

  • CPU architecture: x86-64
  • CPU name: AMD EPYC 9R14
  • OS: Amazon Linux 2

Test log v1.36.0:

[----------] 15 tests from OCSPTest
[ RUN      ] OCSPTest.TestGoodOCSP
/tmp/guix-build-aws-lc-1.36.0.drv-0/source/crypto/ocsp/ocsp_test.cc:421: Failure
Expected equality of these values:
  126
  ERR_GET_REASON(err)
    Which is: 125
/tmp/guix-build-aws-lc-1.36.0.drv-0/source/crypto/ocsp/ocsp_test.cc:423: Failure
Expected equality of these values:
  125
  ERR_GET_REASON(err)
    Which is: 126

Test log v1.34.2:

[----------] 15 tests from OCSPTest
[ RUN      ] OCSPTest.TestGoodOCSP
/tmp/guix-build-aws-lc-1.34.2.drv-0/source/crypto/ocsp/ocsp_test.cc:441: Failure
Expected equality of these values:
  126
  ERR_GET_REASON(err)
    Which is: 125
/tmp/guix-build-aws-lc-1.34.2.drv-0/source/crypto/ocsp/ocsp_test.cc:443: Failure
Expected equality of these values:
  125
  ERR_GET_REASON(err)
    Which is: 126
[  FAILED  ] OCSPTest.TestGoodOCSP (0 ms)
@samuel40791765
Copy link
Contributor

Thanks for reporting this! We were trying to avoid testing time-bombs when developing this, but didn't realize that the offset could trigger the inverse happening when the checked time-field is outdated. I'll put up a change to fix this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants