Skip to content

test(oracledb): retry stalled ESM subprocesses - #10096

Merged
bengl merged 4 commits into
masterfrom
BridgeAR/2026-09-01-oracle-esm-timeout
Sep 8, 2026
Merged

bengl merged 4 commits into
masterfrom
BridgeAR/2026-09-01-oracle-esm-timeout

Conversation

@BridgeAR

@BridgeAR BridgeAR commented Sep 1, 2026

Copy link
Copy Markdown
Member

An Oracle ESM subprocess can stall before exit. The completion-only helper did not expose its child, so teardown could not stop it before Mocha's timeout.

Short-lived subprocess helpers now expose the child before completion. Each bounded Oracle attempt stops its child before one fresh-process retry, and other failures remain terminal.

Refs: oracle/node-oracledb#1592

@dd-octo-sts

dd-octo-sts Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Overall package size

Self size: 8.85 MB
Deduped: 9.52 MB
No deduping: 9.52 MB

Dependency sizes | name | version | self size | total size | |------|---------|-----------|------------| | import-in-the-middle | 3.4.0 | 127.33 kB | 447.04 kB | | opentracing | 0.14.7 | 194.81 kB | 194.81 kB | | dc-polyfill | 0.1.11 | 25.74 kB | 25.74 kB |

🤖 This report was automatically generated by heaviest-objects-in-the-universe

@datadog-prod-us1-6

datadog-prod-us1-6 Bot commented Sep 1, 2026

Copy link
Copy Markdown

Pipelines  Tests

⚠️ Warnings

⚠️ Your PR has warnings. Please review the issues below.

🚦 1 Pipeline job failed

All Green | all-green

View more details · View in GitHub Actions

State is still pending after 30 retries. Cancelling still-running workflows.

ℹ️ Info

No other issues found (see more)

🧪 All tests passed
❄️ No new flaky tests detected

🔄 Datadog retried 1 test - 1 passed on retry View in Datadog

🎯 Code Coverage (details)
Patch Coverage: 100.00%
Overall Coverage: 87.74% (-0.00%)

Useful? React with 👍 / 👎

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 883c71c | Docs | View more details | Give us feedback!

@codecov

codecov Bot commented Sep 1, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.67%. Comparing base (45e9b76) to head (883c71c).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #10096       +/-   ##
===========================================
+ Coverage   87.76%   98.67%   +10.91%     
===========================================
  Files         996     1006       +10     
  Lines      153294   158039     +4745     
  Branches       74       74               
===========================================
+ Hits       134535   155952    +21417     
+ Misses      18759     2087    -16672     
Flag Coverage Δ
ai-guard 65.00% <ø> (-0.02%) ⬇️
apm-capabilities 63.75% <ø> (ø)
apm-integrations 81.47% <ø> (-0.02%) ⬇️
appsec 58.84% <ø> (-0.01%) ⬇️
debugger 69.82% <ø> (-0.06%) ⬇️
instrumentation 53.70% <ø> (-0.01%) ⬇️
llmobs 79.01% <ø> (-0.02%) ⬇️
master-coverage 98.67% <ø> (?)
openfeature 66.39% <ø> (-0.03%) ⬇️
platform 69.31% <ø> (-0.01%) ⬇️
profiling 66.76% <ø> (-0.03%) ⬇️
serverless 65.73% <ø> (-0.02%) ⬇️
test-optimization 82.81% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@pr-commenter

pr-commenter Bot commented Sep 1, 2026

Copy link
Copy Markdown

Benchmarks

Benchmark execution time: 2026-09-08 16:36:58

Comparing candidate commit 883c71c in PR branch BridgeAR/2026-09-01-oracle-esm-timeout with baseline commit 45e9b76 in branch master.

📊 Benchmarking dashboard

Found 0 performance improvements and 0 performance regressions! Performance is the same for 2308 metrics, 5 unstable metrics.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

  • 🟩 = significantly better candidate vs. baseline
  • 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

Unstable benchmarks

These benchmarks have a confidence interval too wide to call a change; treat them as noise rather than signal.

scenario:appsec-iast-with-vulnerability-iast-enabled-default-config-20

  • unstable max_rss_usage [-24.438MB; +17.219MB] or [-7.066%; +4.979%]

scenario:debugger-line-probe-with-snapshot-default-26

  • unstable max_rss_usage [-8.141MB; +15.923MB] or [-3.478%; +6.802%]

scenario:encoders-0.4-immediate-flush-20

  • unstable max_rss_usage [-6.185MB; +11.408MB] or [-8.083%; +14.908%]

scenario:llmobs-encode-unicode-mixed-20

  • unstable max_rss_usage [-7681.092KB; +7822.692KB] or [-9.623%; +9.800%]

scenario:plugin-graphql-long-with-depth-on-max-26

  • unstable max_rss_usage [-20.229MB; +2.864MB] or [-10.728%; +1.519%]

@BridgeAR
BridgeAR force-pushed the BridgeAR/2026-09-01-oracle-esm-timeout branch from d7ea788 to 1215cb9 Compare September 7, 2026 19:12
@BridgeAR
BridgeAR marked this pull request as ready for review September 7, 2026 19:16
@BridgeAR
BridgeAR requested review from a team as code owners September 7, 2026 19:16
@BridgeAR
BridgeAR requested a review from wconti27 September 7, 2026 19:16

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1215cb907f

ℹ️ 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".

Comment thread packages/datadog-plugin-oracledb/test/integration-test/client.spec.js Outdated
Comment thread packages/datadog-plugin-oracledb/test/integration-test/client.spec.js Outdated
@BridgeAR
BridgeAR force-pushed the BridgeAR/2026-09-01-oracle-esm-timeout branch from 1215cb9 to 14c01ba Compare September 8, 2026 16:00
An Oracle ESM subprocess can stall before exit. The old completion-only result kept its child handle from teardown, so the test hit the outer Mocha timeout.

Each attempt now stops its child at its deadline. Oracle retries only that timeout with a fresh subprocess.

Refs: oracle/node-oracledb#1592
Oracle needs the child handle before completion for teardown, while existing integration tests rely on awaiting the helper directly.
A retry could combine telemetry from one child with a clean exit from another, so the test could pass without one complete instrumented run. Shorter Oracle phase limits keep their failures attributable before the process deadline.
The process deadline must remain above Oracle's 15-second connect and 10-second query limits, so slow but valid operations retain their existing budget. Telemetry and Mocha deadlines follow the process deadline so subprocess failures stay attributable.
@BridgeAR
BridgeAR force-pushed the BridgeAR/2026-09-01-oracle-esm-timeout branch from 14c01ba to 883c71c Compare September 8, 2026 16:24
@bengl
bengl enabled auto-merge (squash) September 8, 2026 16:41
@bengl
bengl merged commit e00af3f into master Sep 8, 2026
1526 of 1536 checks passed
@bengl
bengl deleted the BridgeAR/2026-09-01-oracle-esm-timeout branch September 8, 2026 18:47
This was referenced Sep 9, 2026
BridgeAR added a commit that referenced this pull request Sep 11, 2026
* test(oracledb): retry stalled ESM subprocesses

An Oracle ESM subprocess can stall before exit. The old completion-only result kept its child handle from teardown, so the test hit the outer Mocha timeout.

Each attempt now stops its child at its deadline. Oracle retries only that timeout with a fresh subprocess.

Refs: oracle/node-oracledb#1592

* refactor(test): preserve subprocess helper awaitability

Oracle needs the child handle before completion for teardown, while existing integration tests rely on awaiting the helper directly.

* test(oracledb): remove stalled subprocess retry

A retry could combine telemetry from one child with a clean exit from another, so the test could pass without one complete instrumented run. Shorter Oracle phase limits keep their failures attributable before the process deadline.

* test(oracledb): preserve Oracle operation timeouts

The process deadline must remain above Oracle's 15-second connect and 10-second query limits, so slow but valid operations retain their existing budget. Telemetry and Mocha deadlines follow the process deadline so subprocess failures stay attributable.
BridgeAR added a commit that referenced this pull request Sep 11, 2026
* test(oracledb): retry stalled ESM subprocesses

An Oracle ESM subprocess can stall before exit. The old completion-only result kept its child handle from teardown, so the test hit the outer Mocha timeout.

Each attempt now stops its child at its deadline. Oracle retries only that timeout with a fresh subprocess.

Refs: oracle/node-oracledb#1592

* refactor(test): preserve subprocess helper awaitability

Oracle needs the child handle before completion for teardown, while existing integration tests rely on awaiting the helper directly.

* test(oracledb): remove stalled subprocess retry

A retry could combine telemetry from one child with a clean exit from another, so the test could pass without one complete instrumented run. Shorter Oracle phase limits keep their failures attributable before the process deadline.

* test(oracledb): preserve Oracle operation timeouts

The process deadline must remain above Oracle's 15-second connect and 10-second query limits, so slow but valid operations retain their existing budget. Telemetry and Mocha deadlines follow the process deadline so subprocess failures stay attributable.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants