Repository navigation
Conversation
…ion to --duration, and measures TLS Milestone 43's coverage run kept the nightly job's fixed intervals (a kill every 300 s, a crash every 600 s) in 600 s runs: one kill, and no crash, so recovery from the command log looked barely exercised (CommandLogReplayState 88 of 512 lines). The kill and crash intervals are now duration / 9 and duration / 4 (at least 60 and 120 s), and the security run adds --ssl. Measured again (crash and security, 10 minutes each): command log and recovery 58.7% of lines, from 46.5%; CommandLogReplayState 359 of 512, ReplaySequencer 66 of 97, SslSetup 141 of 348.
This was referenced Nov 10, 2026
Author
|
Superseded by #51, which combines every ENG-30396 PR of this repo into one. This PR's branch is kept, and its description still has this milestone's details and lab results. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Milestone 43's coverage run kept the nightly job's fixed intervals, a kill every 300 s and a crash every 600 s, in runs of 600 s. That gave one kill and no crash per run, so recovery from the command log looked barely exercised:
CommandLogReplayState88 of 512 lines. The security run did not use TLS, soSslSetupstayed at 18 of 348.What it changes
run-coverage.sh's intervals scale with--duration. A kill every duration / 9 and a crash every duration / 4, at least 60 s and 120 s.--ssl.No change to the provider or
run-sqlancer.sh.Coverage (
run-coverage.sh, six runs of 10 minutes, every oracle)CommandLogReplayStateReplaySequencerSslSetupTesting