Repository navigation
chore(ci): run compliance against harness 1.32.0 - #1274
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
SDK performance: posthog-pythonBenchmarks completed. No changes flagged for review. Flags require at least a 5% change in the median and all six pairs agreeing on direction. This is a noise filter, not proof of a performance change or a CI gate. View all results
Values are medians of paired measurements. Not flagged does not mean unchanged. Unavailable means a measurement could not be provided, not zero. Estimated allocation measurements retain their instrumentation uncertainty. RSS measures the whole process, not just SDK allocations; observed peaks are sampled checkpoints. Paired ranges in the diagnostics describe variability, not confidence intervals. Each shard uses its own runner; compare Before PR against With PR within a row, not across shards. Compared 102 metric rows; 102 rows shown in all results. Omitted or shortened data remain in |
turnipdabeets
left a comment
There was a problem hiding this comment.
LGTM. The digest matches the 1.32.0 tag, and compliance passes. The failing Python 3.x tests jobs are the cache_write_tokens OpenAI tests that #1273 fixes, not this change.
💡 Motivation and Context
Harness 1.32.0 (released 2026-11-17) adds retry-recovery and synchronous-delivery profiles and rejects contradictory bounded/unbounded retry capabilities before acceptance (release notes). This runs the compliance suite against it so any new failure shows up here first.
ghcr.io/posthog/sdk-test-harness:1.32.0by digest (was 1.31.1).💚 How did you test it?
This PR's own compliance run is the test. Draft until that run is reviewed; any failure gets classified before this lands.
📝 Checklist
🤖 Agent context
Claude Code (Claude Opus 5.5), human-directed.
🤖 Generated with Claude Code