antithesis(logs): logs-agent research artifacts#51504
Conversation
…ntithesis) Moves antithesis/ -> test/antithesis/ (repo test-tree convention). Contains the research scratchbook (catalog, SUT analysis, evaluation, bug-burndown tracker, run records) and the Antithesis harness scaffold (docker-compose, Dockerfile, build.sh, test template). No Go code. Per-subsystem repro tests are co-local in their packages on the branches above.
…ntithesis) Moves antithesis/ -> test/antithesis/ (repo test-tree convention). Research scratchbook (catalog, SUT analysis, evaluation, bug-burndown tracker incl. subsystem branch map, run records) + Antithesis harness scaffold (compose, Dockerfile, build.sh, test template). No Go code; per-subsystem repro tests are co-local in their packages on the branches above.
|
@codex review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0014d0e4e5
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| CGO_ENABLED=1 go build -tags "antithesis_demo test" \ | ||
| -o "${SCRIPT_DIR}/rotation-demo.bin" \ | ||
| ./pkg/logs/cmd/antithesis-rotation-demo/ |
There was a problem hiding this comment.
The documented Antithesis setup cannot build because this script targets ./pkg/logs/cmd/antithesis-rotation-demo/, but this commit does not add that package and a repo-wide search only finds the name in this new harness/docs. Any user following build.sh before docker compose build will fail before rotation-demo.bin is created, so the Dockerfile's COPY build/rotation-demo/rotation-demo.bin and the Antithesis run are unusable until the demo package is added or the script points at an existing target.
Useful? React with 👍 / 👎.
|
Scratchbook from /antithesis-research on the logs agent: SUT analysis, property catalog, 4-lens evaluation, bug-burndown tracker, run records, and AGENTS.md. No Go code and no harness (the run harness is its own PR, stacked above).
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a9874e6ac8
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| Use the `antithesis-setup` skill to scaffold and manage this directory. Use the `antithesis-research` skill to analyze the system and build a property catalog. Use the `antithesis-workload` skill to implement assertions and test commands. Use the `antithesis-launch` skill to build, validate, and submit Antithesis runs — do not run `snouty launch` directly. | ||
|
|
||
| **snouty launch** | ||
| Use `snouty launch --json --webhook basic_test --config test/antithesis/config` to start an Antithesis run. Always run `compose build` first to ensure images are up to date. |
There was a problem hiding this comment.
In this commit the test/antithesis tree contains only AGENTS.md and scratchbook/ files; there is no test/antithesis/config directory or docker-compose.yaml for this launch command to consume. Anyone following this new harness guidance will hit a missing-config failure before Antithesis can start, so either include the scaffolded config in the commit or mark the launch instructions as future work until the directory exists.
Useful? React with 👍 / 👎.
| Tracks every suspected bug from the property catalog to a terminal state. Statuses: | ||
|
|
||
| - **REPRO-LOCAL** — reproduced by a build-tagged `antithesis_demo` test against real | ||
| Agent code (run with `go test -tags "antithesis_demo test"`). |
There was a problem hiding this comment.
The repo-wide AGENTS.md explicitly forbids raw go test/go build because the Agent relies on custom build tags computed by dda inv; this new reproduction recipe bypasses that wrapper, so future users may get misleading compile/test results for these demo paths. Please rewrite the scratchbook commands to use dda inv test --targets=... (and avoid the later plain-go build recommendation for the same reason).
Useful? React with 👍 / 👎.
Files inventory check summaryFile checks results against ancestor 8ff8f30e: Results for datadog-agent_7.81.0~devel.git.307.a9874e6.pipeline.115942035-1_amd64.deb:No change detected |
blt
changed the title
blt
added
changelog/no-changelog
1 participant
What does this PR do?
This PR introduces the artifacts that result from
/antithesis-researchdirected to focus on the logs Agent.Motivation
My goal is to run Agent componnts through antithesis shots. The first target overlaps with @cmetz100 's SMP Forward Deploy effort.
Describe how you validated your changes
N/A
Additional Notes
The artifacts here are quite verbose, unclear to me whether we should preserve the research skill's interior material in-repo or land it in a sibling repo and extract or what. Will ping Antithesis for guidance.