- Notifications
You must be signed in to change notification settings - Fork928
test: Regenerate GitSSHKey flake when comparing times#1235
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This is a crazy one! The in-memory DB is fast, which allows the sameexact timestamp to occur for regenerating the key!See:https://github.com/coder/coder/runs/6234173911?check_suite_focus=true#step:9:82
Happened in#1231 |
codecovbot commentedApr 29, 2022 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Codecov Report
@@ Coverage Diff @@## main #1235 +/- ##==========================================+ Coverage 65.33% 65.76% +0.43%========================================== Files 266 272 +6 Lines 17651 17872 +221 Branches 192 192 ==========================================+ Hits 11532 11754 +222- Misses 4880 4886 +6+ Partials 1239 1232 -7
Continue to review full report at Codecov.
|
This is a crazy one! The in-memory DB is fast, which allows the sameexact timestamp to occur for regenerating the key!See:https://github.com/coder/coder/runs/6234173911?check_suite_focus=true#step:9:82
This is a crazy one! The in-memory DB is fast, which allows the same
exact timestamp to occur for regenerating the key!
See:https://github.com/coder/coder/runs/6234173911?check_suite_focus=true#step:9:82