Skip to content

ENG-30396: run-coverage.sh kills and crashes in proportion to the run, and measures TLS (milestone 44) - #43

Closed
jwiebema1 wants to merge 1 commit into
ENG-30396-sqlancer-m43from
ENG-30396-sqlancer-m44
Closed

jwiebema1 wants to merge 1 commit into
ENG-30396-sqlancer-m43from
ENG-30396-sqlancer-m44

Conversation

@jwiebema1

Copy link
Copy Markdown

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: CommandLogReplayState 88 of 512 lines. The security run did not use TLS, so SslSetup stayed 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.
  • The security run adds --ssl.
  • README: the coverage numbers below.

No change to the provider or run-sqlancer.sh.

Coverage (run-coverage.sh, six runs of 10 minutes, every oracle)

Area or class Milestone 43 Milestone 44
Command log and recovery, lines 46.5% 64.2%
CommandLogReplayState 88 of 512 359 of 512
ReplaySequencer 66 of 97
SslSetup 18 of 348 141 of 348
Elastic resize, lines 69.6% 69.3%
Rejoin, lines 74.4%
DR and XDCR, lines 52.2% 52.6%
Export and streams, lines 32.4% 32.5%
Security, lines 23.4%

Testing

  • The six coverage runs passed. The kill and resize runs were run twice, because something outside the test killed every VoltDB server on the machine in the same instant during the first attempt (no FATAL line, no crash file). The rerun had 7 kills, 7 rejoins, 2 grows and 2 shrinks.
  • Lab build Integrate SQLite into the CI sqlancer/sqlancer#58 ran this branch's descendant (milestone 45, 37f2218); see that PR.

…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.
@jwiebema1

Copy link
Copy Markdown
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.

@jwiebema1 jwiebema1 closed this Nov 18, 2026
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 this pull request may close these issues.

1 participant