Skip to content

feat(test-optimization): diagnose and fix Jest suite skipping#9339

Merged
juan-fernandez merged 1 commit into
masterfrom
juan-fernandez/log-skippable-coverage-filtering
Jul 15, 2026
Merged

feat(test-optimization): diagnose and fix Jest suite skipping#9339
juan-fernandez merged 1 commit into
masterfrom
juan-fernandez/log-skippable-coverage-filtering

Conversation

@juan-fernandez

@juan-fernandez juan-fernandez commented Jul 14, 2026

Copy link
Copy Markdown
Collaborator

What does this PR do?

Logs counts for skippable candidates received, excluded because line coverage is missing, and retained. It warns when coverage filtering removes every candidate and expands the Jest debug message with discovered, candidate, skipped, and runnable suite counts. The same response summary is logged for HTTP-cache responses without logging test names or the full endpoint payload.

Fixes Jest suite matching when Jest runs below the repository root. Suite identifiers are matched relative to Jest's rootDir, while coverage backfill continues to use repository-relative paths. Received suite paths are also normalized so historical Windows identifiers containing backslashes remain compatible.

Adds DD_CIVISIBILITY_CODE_COVERAGE_REPORT_UPLOAD_ENABLED=false as an internal kill switch for the backend coverage_report_upload_enabled setting. The default value is true, which preserves backend authority and does not force-enable upload when the backend disables it.

Motivation

A Jest run received a non-empty skippable-suite response but still ran every discovered suite. The client compared repository-relative paths against backend suite identifiers relative to Jest's root using exact string matching. Historical Windows identifiers could additionally contain mixed slash directions.

The diagnostics distinguish an empty backend response, client-side line-coverage filtering, and a suite-path mismatch. The kill switch makes it possible to isolate coverage-report-upload behavior without disabling TIA coverage collection or changing the remote setting.

@dd-octo-sts

dd-octo-sts Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Overall package size

Self size: 6.77 MB
Deduped: 7.43 MB
No deduping: 7.43 MB

Dependency sizes | name | version | self size | total size | |------|---------|-----------|------------| | import-in-the-middle | 3.3.1 | 122.62 kB | 438.86 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

@pr-commenter

pr-commenter Bot commented Jul 14, 2026

Copy link
Copy Markdown

Benchmarks

Benchmark execution time: 2026-07-15 12:27:45

Comparing candidate commit 934be27 in PR branch juan-fernandez/log-skippable-coverage-filtering with baseline commit 7f6c836 in branch master.

📊 Benchmarking dashboard

Found 0 performance improvements and 0 performance regressions! Performance is the same for 2315 metrics, 43 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-appsec-enabled-24

  • unstable execution_time [-207114.286µs; +205833.719µs] or [-7.810%; +7.762%]

scenario:appsec-appsec-enabled-26

  • unstable execution_time [-236.302ms; +228.259ms] or [-9.259%; +8.944%]

scenario:appsec-appsec-enabled-with-attacks-24

  • unstable execution_time [-165.789ms; +159.778ms] or [-5.366%; +5.172%]

scenario:appsec-appsec-enabled-with-attacks-26

  • unstable execution_time [-186.300ms; +190.486ms] or [-6.439%; +6.584%]

scenario:appsec-control-20

  • unstable execution_time [-114.601ms; +133.207ms] or [-6.989%; +8.124%]

scenario:appsec-control-24

  • unstable execution_time [-111.911ms; +117.116ms] or [-9.027%; +9.447%]

scenario:appsec-control-26

  • unstable execution_time [-123876.235µs; +125331.235µs] or [-9.998%; +10.115%]

scenario:appsec-iast-no-vulnerability-control-20

  • unstable execution_time [-12.328ms; +17.802ms] or [-4.802%; +6.935%]

scenario:appsec-iast-no-vulnerability-iast-enabled-always-active-20

  • unstable execution_time [-18.731ms; +11.190ms] or [-7.293%; +4.357%]

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

  • unstable execution_time [-12.911ms; +20.786ms] or [-4.977%; +8.014%]

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

  • unstable execution_time [-26.893ms; +32.903ms] or [-4.917%; +6.016%]

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

  • unstable instructions [-3377.8M instructions; +3312.4M instructions] or [-5.117%; +5.018%]

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

  • unstable cpu_user_time [-3894.219ms; +2364.963ms] or [-36.184%; +21.974%]
  • unstable execution_time [-3938.916ms; +2356.510ms] or [-34.250%; +20.491%]
  • unstable instructions [-34.6G instructions; +20.9G instructions] or [-38.249%; +23.149%]
  • unstable max_rss_usage [-11.672MB; +7.813MB] or [-7.132%; +4.774%]
  • unstable throughput [-509.797op/s; +831.892op/s] or [-17.233%; +28.122%]

scenario:debugger-line-probe-with-snapshot-minimal-24

  • unstable instructions [-4010.3M instructions; +3029.6M instructions] or [-6.009%; +4.539%]

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

  • unstable cpu_user_time [-2511.388ms; +815.259ms] or [-26.034%; +8.451%]
  • unstable execution_time [-2550.472ms; +794.405ms] or [-24.594%; +7.660%]
  • unstable instructions [-22.5G instructions; +7.3G instructions] or [-27.936%; +9.131%]
  • unstable throughput [-137.465op/s; +458.855op/s] or [-4.270%; +14.253%]

scenario:debugger-line-probe-without-snapshot-24

  • unstable cpu_user_time [-1494.803ms; +598.244ms] or [-18.080%; +7.236%]
  • unstable execution_time [-1564.571ms; +651.687ms] or [-17.439%; +7.264%]
  • unstable instructions [-12.5G instructions; +5.0G instructions] or [-18.538%; +7.477%]
  • unstable throughput [-211.283op/s; +438.005op/s] or [-5.774%; +11.970%]

scenario:debugger-line-probe-without-snapshot-26

  • unstable cpu_user_time [-3.545s; +0.501s] or [-34.272%; +4.840%]
  • unstable execution_time [-3.567s; +0.548s] or [-32.189%; +4.946%]
  • unstable instructions [-31.6G instructions; +4.2G instructions] or [-36.497%; +4.862%]
  • unstable throughput [-119.202op/s; +686.791op/s] or [-3.886%; +22.388%]

scenario:dogstatsd-aggregated-26

  • unstable cpu_usage_percentage [-6.437%; +3.972%]
  • unstable execution_time [-53.380ms; +86.114ms] or [-5.274%; +8.508%]
  • unstable throughput [-960755.706op/s; +596447.286op/s] or [-6.407%; +3.978%]

scenario:dogstatsd-with-tags-20

  • unstable cpu_user_time [-189.402ms; +424.088ms] or [-3.861%; +8.645%]
  • unstable execution_time [-190.651ms; +424.418ms] or [-3.829%; +8.525%]
  • unstable throughput [-150054.933op/s; +67729.748op/s] or [-8.906%; +4.020%]

scenario:plugin-claude-agent-sdk-compact-stream-scan-24

  • unstable cpu_usage_percentage [-4.549%; +5.559%]

scenario:plugin-claude-agent-sdk-compact-stream-scan-26

  • unstable cpu_usage_percentage [-6.538%; +3.486%]

scenario:plugin-graphql-long-with-depth-off-20

  • unstable max_rss_usage [-8.658MB; +4.915MB] or [-6.674%; +3.788%]

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

  • unstable cpu_user_time [-722.560ms; +732.656ms] or [-5.613%; +5.691%]
  • unstable execution_time [-730.327ms; +745.283ms] or [-5.542%; +5.655%]
  • unstable throughput [-3.403op/s; +3.312op/s] or [-5.570%; +5.421%]

scenario:test-optimization-large-suite-20

  • unstable max_rss_usage [-4189.143KB; +4203.476KB] or [-5.285%; +5.303%]

@datadog-datadog-prod-us1-2

datadog-datadog-prod-us1-2 Bot commented Jul 14, 2026

Copy link
Copy Markdown

Tests

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
Patch Coverage: 96.94%
Overall Coverage: 96.61% (-0.00%)

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 934be27 | Docs | Datadog PR Page | Give us feedback!

@codecov

codecov Bot commented Jul 14, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 96.93878% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 96.64%. Comparing base (7f6c836) to head (934be27).
⚠️ Report is 19 commits behind head on master.

Files with missing lines Patch % Lines
...ty/intelligent-test-runner/get-skippable-suites.js 94.54% 3 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #9339      +/-   ##
==========================================
+ Coverage   96.61%   96.64%   +0.03%     
==========================================
  Files         920      923       +3     
  Lines      122236   122937     +701     
  Branches    21077    21270     +193     
==========================================
+ Hits       118097   118817     +720     
+ Misses       4139     4120      -19     
Flag Coverage Δ
aiguard 53.65% <ø> (+0.05%) ⬆️
aiguard-integration 57.10% <ø> (+0.13%) ⬆️
apm-bucket-0 53.88% <ø> (+0.05%) ⬆️
apm-bucket-1 58.45% <ø> (+0.42%) ⬆️
apm-bucket-2 56.18% <ø> (+0.04%) ⬆️
apm-capabilities-tracing 60.65% <95.52%> (+0.29%) ⬆️
apm-integrations-aerospike 53.03% <ø> (+0.06%) ⬆️
apm-integrations-confluentinc-kafka-javascript 57.12% <ø> (+0.09%) ⬆️
apm-integrations-couchbase 53.37% <ø> (+0.05%) ⬆️
apm-integrations-http 58.04% <ø> (+0.06%) ⬆️
apm-integrations-kafkajs 57.83% <ø> (+0.09%) ⬆️
apm-integrations-next 54.26% <ø> (-0.02%) ⬇️
apm-integrations-prisma 54.26% <ø> (+0.04%) ⬆️
apm-integrations-tedious 53.14% <ø> (+0.05%) ⬆️
appsec 68.92% <ø> (-0.05%) ⬇️
appsec-express_fastify_graphql 65.74% <ø> (+0.04%) ⬆️
appsec-integration 51.93% <0.00%> (+0.07%) ⬆️
appsec-kafka_ldapjs_lodash 59.17% <ø> (+0.06%) ⬆️
appsec-mongodb-core_mongoose_mysql 62.40% <ø> (+0.14%) ⬆️
appsec-next 52.85% <0.00%> (-0.03%) ⬇️
appsec-node-serialize_passport_postgres 62.04% <ø> (+0.15%) ⬆️
appsec-sourcing_stripe_template 60.43% <ø> (+0.08%) ⬆️
debugger 65.70% <ø> (-0.06%) ⬇️
instrumentations-bucket-0 48.88% <ø> (+0.08%) ⬆️
instrumentations-bucket-1 55.08% <ø> (+0.09%) ⬆️
instrumentations-bucket-10 56.71% <ø> (+0.05%) ⬆️
instrumentations-bucket-11 48.87% <ø> (+0.08%) ⬆️
instrumentations-bucket-12 49.05% <ø> (+0.15%) ⬆️
instrumentations-bucket-13 48.81% <ø> (+0.08%) ⬆️
instrumentations-bucket-2 50.02% <ø> (+0.23%) ⬆️
instrumentations-bucket-3 53.99% <ø> (+0.12%) ⬆️
instrumentations-bucket-4 49.29% <ø> (+0.08%) ⬆️
instrumentations-bucket-5 53.14% <0.00%> (+0.09%) ⬆️
instrumentations-bucket-6 55.73% <ø> (+0.09%) ⬆️
instrumentations-bucket-7 53.64% <ø> (-0.01%) ⬇️
instrumentations-bucket-8 54.76% <ø> (+0.09%) ⬆️
instrumentations-bucket-9 56.19% <ø> (+0.06%) ⬆️
instrumentations-instrumentation-couchbase 48.27% <ø> (+0.09%) ⬆️
instrumentations-integration-esbuild 34.05% <0.00%> (+0.15%) ⬆️
llmobs-ai_anthropic_bedrock 57.77% <ø> (+<0.01%) ⬆️
llmobs-bucket-1 57.11% <ø> (+0.07%) ⬆️
llmobs-openai 57.50% <ø> (+0.07%) ⬆️
llmobs-sdk 60.07% <ø> (+0.06%) ⬆️
llmobs-vertex-ai 54.31% <ø> (+0.05%) ⬆️
master-coverage 96.64% <96.93%> (?)
openfeature 54.70% <ø> (+0.10%) ⬆️
openfeature-unit 49.91% <ø> (+0.08%) ⬆️
platform-core_esbuild_instrumentations-misc 38.52% <0.00%> (+0.12%) ⬆️
platform-integration 62.32% <ø> (-0.01%) ⬇️
platform-shimmer_unit-guardrails_webpack 37.32% <0.00%> (+0.09%) ⬆️
plugins-bucket-0 53.26% <ø> (+0.04%) ⬆️
plugins-bucket-1 55.20% <ø> (+0.17%) ⬆️
plugins-bucket-11 57.53% <ø> (+0.04%) ⬆️
plugins-bucket-18 57.14% <ø> (+0.04%) ⬆️
plugins-bucket-19 55.47% <ø> (+0.08%) ⬆️
plugins-bucket-20 57.66% <ø> (+0.19%) ⬆️
plugins-bucket-4 53.87% <ø> (-0.02%) ⬇️
plugins-bullmq_cassandra_cookie 57.47% <ø> (+0.09%) ⬆️
plugins-cookie-parser_crypto_dd-trace-api 52.42% <ø> (+0.06%) ⬆️
plugins-fetch_fs_generic-pool 54.59% <ø> (+0.09%) ⬆️
plugins-google-cloud-pubsub_grpc_handlebars 59.92% <ø> (+0.03%) ⬆️
plugins-hapi_hono_ioredis 55.86% <ø> (-0.04%) ⬇️
plugins-jest_knex_langgraph 51.79% <100.00%> (+0.08%) ⬆️
plugins-ldapjs_light-my-request_limitd-client 53.51% <ø> (+0.05%) ⬆️
plugins-lodash_mariadb_memcached 54.30% <ø> (+0.05%) ⬆️
plugins-moleculer_mongodb_mongodb-core 57.40% <ø> (+0.08%) ⬆️
plugins-mongoose_multer_mysql 54.79% <ø> (+0.04%) ⬆️
plugins-mysql2_nats_node-serialize 56.33% <ø> (+0.09%) ⬆️
plugins-opensearch_passport-http_pino 55.19% <ø> (+0.10%) ⬆️
plugins-postgres_process_pug 54.38% <ø> (+0.05%) ⬆️
plugins-redis_router_sequelize 57.19% <ø> (+0.12%) ⬆️
plugins-test-and-upstream-rhea_undici_url 57.04% <ø> (-0.02%) ⬇️
plugins-valkey_vm_winston 54.02% <ø> (+0.14%) ⬆️
plugins-ws 54.93% <ø> (+0.09%) ⬆️
profiling 58.26% <ø> (-0.01%) ⬇️
serverless-aws-sdk-aws-sdk 50.76% <0.00%> (+0.05%) ⬆️
serverless-aws-sdk-bedrockruntime 50.75% <ø> (+0.02%) ⬆️
serverless-aws-sdk-client 52.09% <ø> (+0.11%) ⬆️
serverless-aws-sdk-dynamodb 51.80% <ø> (+0.01%) ⬆️
serverless-aws-sdk-eventbridge 46.44% <0.00%> (+0.18%) ⬆️
serverless-aws-sdk-kinesis 54.79% <ø> (+0.05%) ⬆️
serverless-aws-sdk-lambda 52.87% <ø> (+0.05%) ⬆️
serverless-aws-sdk-s3 51.59% <ø> (+0.01%) ⬆️
serverless-aws-sdk-serverless-peer-service 54.82% <ø> (+0.06%) ⬆️
serverless-aws-sdk-sns 55.54% <ø> (+0.03%) ⬆️
serverless-aws-sdk-sqs 56.04% <ø> (+0.09%) ⬆️
serverless-aws-sdk-stepfunctions 51.36% <ø> (+0.06%) ⬆️
serverless-aws-sdk-util 48.54% <ø> (+0.05%) ⬆️
serverless-bucket-0 55.24% <ø> (+0.07%) ⬆️
serverless-bucket-1 56.06% <ø> (+0.01%) ⬆️
test-optimization-cucumber 73.03% <60.22%> (+0.10%) ⬆️
test-optimization-cypress 66.43% <69.31%> (+0.15%) ⬆️
test-optimization-jest 74.40% <83.67%> (+0.15%) ⬆️
test-optimization-mocha 74.73% <62.50%> (+0.12%) ⬆️
test-optimization-playwright-playwright-atr 61.44% <22.72%> (+<0.01%) ⬆️
test-optimization-playwright-playwright-efd 61.64% <22.72%> (-0.05%) ⬇️
test-optimization-playwright-playwright-final-status 61.61% <22.72%> (-0.03%) ⬇️
test-optimization-playwright-playwright-impacted-tests 61.33% <22.72%> (+0.07%) ⬆️
test-optimization-playwright-playwright-reporting 61.21% <22.72%> (-0.07%) ⬇️
test-optimization-playwright-playwright-test-management 62.17% <22.72%> (-0.22%) ⬇️
test-optimization-playwright-playwright-test-span 61.36% <22.72%> (-0.08%) ⬇️
test-optimization-selenium 60.74% <47.95%> (-0.04%) ⬇️
test-optimization-testopt 59.23% <77.55%> (+0.18%) ⬆️
test-optimization-vitest 71.33% <23.86%> (-0.19%) ⬇️

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.

@juan-fernandez juan-fernandez changed the title fix(test-optimization): log filtered TIA candidates fix(test-optimization): add TIA coverage diagnostics and kill switch Jul 14, 2026
@juan-fernandez

Copy link
Copy Markdown
Collaborator Author

@codex review

@juan-fernandez
juan-fernandez marked this pull request as ready for review July 14, 2026 19:09
@juan-fernandez
juan-fernandez requested review from a team as code owners July 14, 2026 19:09
@juan-fernandez
juan-fernandez requested review from BridgeAR and removed request for a team July 14, 2026 19:09

@datadog-datadog-prod-us1-2 datadog-datadog-prod-us1-2 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.

Datadog Autotest: PASS

More details

The PR adds diagnostic logging and a kill switch for coverage-report-upload filtering. Critical scenario validated: when all TIA candidates have missing line coverage and upload is enabled, candidates are correctly filtered and a warning is logged for operator visibility. The kill switch preserves backend authority by default while allowing operators to bypass filtering when needed.

Was this helpful? React 👍 or 👎

📊 Validated against 15 scenarios · Open Bits AI session

🤖 Datadog Autotest · Commit 4034003 · What is Autotest? · Any feedback? Reach out in #autotest

@BridgeAR BridgeAR changed the title fix(test-optimization): add TIA coverage diagnostics and kill switch feat(test-optimization): add TIA coverage diagnostics and kill switch Jul 14, 2026

@BridgeAR BridgeAR left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

It is a bit difficult to read for me, while I believe the code is fine as is. We might want to add a few more test cases to have all permutations in the tests :)

I changed it from fix to feature due to the added config.

@juan-fernandez
juan-fernandez marked this pull request as draft July 15, 2026 09:01
@juan-fernandez juan-fernandez changed the title feat(test-optimization): add TIA coverage diagnostics and kill switch feat(test-optimization): diagnose and fix Jest suite skipping Jul 15, 2026
@datadog-datadog-prod-us1-2

datadog-datadog-prod-us1-2 Bot commented Jul 15, 2026

Copy link
Copy Markdown

View session in Datadog

Bits Code status: ✅ Done

Comment @DataDog to request changes

@juan-fernandez
juan-fernandez force-pushed the juan-fernandez/log-skippable-coverage-filtering branch from 54b2523 to 204e19a Compare July 15, 2026 11:24
@juan-fernandez
juan-fernandez marked this pull request as ready for review July 15, 2026 11:24

@datadog-datadog-prod-us1-2 datadog-datadog-prod-us1-2 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.

Datadog Autotest: PASS

More details

The PR correctly addresses Jest suite skipping when Jest runs below the repository root by separating suite-matching paths from coverage-backfill paths. Existing tests all pass, and adversarial scenarios confirm the Windows path normalization, environment variable kill-switch, and coverage-filtering counters work as intended. The change introduces diagnostic logging to distinguish empty backend responses, coverage filtering, and path mismatches — key for debugging the reported issue where Jest skipped all suites despite receiving skippable candidates.

Was this helpful? React 👍 or 👎

📊 Validated against 7 scenarios · Open Bits AI session

🤖 Datadog Autotest · Commit 204e19a · What is Autotest? · Any feedback? Reach out in #autotest

@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: 204e19a0d6

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread packages/datadog-instrumentations/src/jest.js Outdated
Comment thread packages/datadog-plugin-jest/src/util.js
@juan-fernandez
juan-fernandez force-pushed the juan-fernandez/log-skippable-coverage-filtering branch from 204e19a to 2302a88 Compare July 15, 2026 11:51
@juan-fernandez

Copy link
Copy Markdown
Collaborator Author

@codex review

@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: 2302a88b73

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread packages/datadog-plugin-jest/src/util.js Outdated
Comment thread packages/datadog-plugin-jest/src/util.js
@juan-fernandez
juan-fernandez force-pushed the juan-fernandez/log-skippable-coverage-filtering branch from 2302a88 to 934be27 Compare July 15, 2026 12:13
@juan-fernandez

Copy link
Copy Markdown
Collaborator Author

@codex review

1 similar comment
@juan-fernandez

Copy link
Copy Markdown
Collaborator Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Swish!

Reviewed commit: 934be275bc

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@juan-fernandez
juan-fernandez merged commit 61f293b into master Jul 15, 2026
657 checks passed
@juan-fernandez
juan-fernandez deleted the juan-fernandez/log-skippable-coverage-filtering branch July 15, 2026 13:10
@dd-octo-sts dd-octo-sts Bot mentioned this pull request Jul 16, 2026
@dd-octo-sts dd-octo-sts Bot mentioned this pull request Jul 16, 2026
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.

3 participants