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

Test last_probe_time_should_advance is flakey #1158

Open
ximon18 opened this issue Nov 15, 2023 · 1 comment
Open

Test last_probe_time_should_advance is flakey #1158

ximon18 opened this issue Nov 15, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@ximon18
Copy link
Member

ximon18 commented Nov 15, 2023

From: https://github.com/NLnetLabs/krill/actions/runs/6655929088/job/18110471770#step:5:1005

---- commons::crypto::signing::signers::probe::tests::last_probe_time_should_advance stdout ----
Error: thread 'main' panicked at 'assertion failed: t2 == t1', src/commons/crypto/signing/signers/probe.rs:355:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

This failed in a test run in which the change made seems unrelated to the failure.

@ximon18
Copy link
Member Author

ximon18 commented Nov 15, 2023

The durations used in the test were increased recently to work around this, but a proper fix will require removing the dependence on elapsed time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Development

No branches or pull requests

2 participants