Rewrite readiness-probe comment to be bug-agnostic#64
Rewrite readiness-probe comment to be bug-agnostic#64pawelchcki wants to merge 1 commit intopc/test-hang-fixfrom
Conversation
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
a38dc0a to
99e8f12
Compare
f8b5e63 to
79ee32d
Compare
79ee32d to
830ce2b
Compare
6a34305 to
9f8d21d
Compare
0791740 to
546027b
Compare
9f8d21d to
2d7e81a
Compare
546027b to
cf1d98d
Compare
2d7e81a to
a3cf24d
Compare
cf1d98d to
74e3eec
Compare
a3cf24d to
6db78f7
Compare
There was a problem hiding this comment.
Pull request overview
Updates the integration test harness documentation to explain why readiness is probed via TCP (instead of HTTP) in a way that remains accurate even as mod_datadog internals evolve.
Changes:
- Rewrites the readiness-probe comment to be bug-agnostic and focused on handler/trace side effects.
- Clarifies that HTTP probes may generate traces in the per-test agent session, while raw TCP connect does not.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| # Probe readiness with a bare TCP connect rather than an HTTP GET: | ||
| # HTTP probes run through mod_datadog's handlers and can emit a | ||
| # trace into the per-test agent session, contaminating assertions | ||
| # tests make about per-request trace counts. A raw TCP connect |
There was a problem hiding this comment.
Minor grammar: consider adding “that” to clarify the sentence (“…can emit a trace into the per-test agent session, contaminating assertions that tests make about per-request trace counts.”).
| # tests make about per-request trace counts. A raw TCP connect | |
| # that tests make about per-request trace counts. A raw TCP connect |
74e3eec to
c03a185
Compare
6db78f7 to
b20bf17
Compare
|
🎯 Code Coverage (details) 🔗 Commit SHA: 33d9e1c | Docs | Datadog PR Page | Give us feedback! |
b20bf17 to
bd7f943
Compare
c03a185 to
100093b
Compare
bd7f943 to
ad645a1
Compare
100093b to
886f1c6
Compare
ad645a1 to
5ea1662
Compare
886f1c6 to
27ea853
Compare
5ea1662 to
b636ade
Compare
27ea853 to
e4163a4
Compare
The previous comment explained the TCP-over-HTTP choice by citing a specific bug in the DatadogTracing Off scope-merge path. That bug is now fixed, so the comment reads as if a live bug is still in the tree. Restate the rationale in terms that will still be true after further mod_datadog changes: any HTTP probe runs through the module's handlers and can emit a trace into the per-test agent session; a bare TCP connect can't.
e4163a4 to
33d9e1c
Compare
b636ade to
c5d42da
Compare

The readiness-probe comment cited a specific bug in the
DatadogTracing Offscope-merge path to justify using TCP over HTTP. That bug is fixed earlier in this stack, so the comment now reads as if a live bug is still in the tree.Restate the rationale bug-agnostically: any HTTP probe runs through the module's handlers and can emit a trace into the per-test agent session; a bare TCP connect can't. This stays true regardless of future mod_datadog changes.