Repository navigation
Record the rest of the game day, and say what it found - #69
Merged
Merged
Conversation
Five rows join results.tsv. Three are scenario 2 at the new 83 percent target: two ran on 2026-09-22 after PR #65 but only ever reached SSM's output, and one ran on 2026-09-23. All three went the same way: DiskAlmostFull pending at 45 to 60 s, firing at 646 to 661 s, cleared by itself about 60 s after the filler was removed. Two are scenario 3 on staging. The first measured nothing: the indexer Job is incremental, nothing had changed since the last sync, so it finished in 60 s with the chunk count unchanged and the index age still climbing. It also overlapped the third disk run. The second followed a desktop vault sync of 56 changed notes: 409 chunks added in 181 s, the API's index age back to 0 while the Job was still writing, canary at 1.00 throughout, no failed readiness check. PR #25's reopen held. The README said nothing had been run and that scenario 4 could only report no-card. Both were stale: it now opens with what each scenario found, says why scenario 3 needs a vault sync before every run, and records when the cloud scorecard was taken.
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
1 participant
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.
Finishes the game day's measured part. Data and docs only, no script changes.
What's in it
deploy/gameday/results.tsvgets five rows:The two 09-22 disk runs finished on the node after PR #65 but only ever reached SSM's command output. They were read back from
aws ssm list-command-invocations(commands5804eaf1,097fac2a).deploy/gameday/README.md:Not done
--fullvariant of the script. The variant isn't built.cost.md's measured row. Both wait for the nextops.py upand for September to close.Report
Paradigm: none. Data rows and prose, no code unit changed.
Changed:
deploy/gameday/results.tsv(5 rows),deploy/gameday/README.md(3 sections).Rules applied: FP-01, results kept as inert data in the file the scripts already read their header from. The field count of every row was checked against the header before writing.
Verified: every number is copied from the scripts' own result rows (SSM output for the 09-22 runs,
send_command.pyoutput for the 09-23 runs). Rows read back from the file: 11 columns, 12 rows.Unverified: CI hasn't run on this branch yet.
Deviations: scenario 3 has two runs where PLAN.md asks for three, and the first overlapped a disk run. Both are stated in the README instead of being dropped.