Skip to content

Update & Rerun Benchmarks#322

Merged
vsanthanam merged 1 commit intomainfrom
vsanthanam/update-benchmarks
Jan 16, 2026
Merged

Update & Rerun Benchmarks#322
vsanthanam merged 1 commit intomainfrom
vsanthanam/update-benchmarks

Conversation

@vsanthanam
Copy link
Copy Markdown
Owner

No description provided.

Copy link
Copy Markdown

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

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: bf7624676d

ℹ️ 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 on lines +53 to +55
"array",
"canada",
"twitter"
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Fix benchmark resource name mismatch for new files

The new entries array, canada, and twitter are passed through load(benchmark:), which always prefixes the resource name as benchmark-<name>. That means this will look for benchmark-array.json, benchmark-canada.json, and benchmark-twitter.json, but the added resources are named array.json, canada.json, and twitter.json. When running benchmarks, Bundle.module.url(forResource:withExtension:) returns nil and the force unwrap crashes before any benchmarks run. Either rename the files to include the benchmark- prefix or adjust load to avoid the prefix for these entries.

Useful? React with 👍 / 👎.

@codecov
Copy link
Copy Markdown

codecov bot commented Jan 16, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.72%. Comparing base (097bcb3) to head (0be70b1).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #322   +/-   ##
=======================================
  Coverage   94.72%   94.72%           
=======================================
  Files          35       35           
  Lines        2879     2879           
=======================================
  Hits         2727     2727           
  Misses        152      152           
Flag Coverage Δ
llvm-cov 94.72% <ø> (ø)
swiftpm 94.72% <ø> (ø)

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

☔ View full report in Codecov by Sentry.
📢 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.

@vsanthanam vsanthanam force-pushed the vsanthanam/update-benchmarks branch from bf76246 to 0be70b1 Compare January 16, 2026 22:55
@vsanthanam vsanthanam merged commit 36d706e into main Jan 16, 2026
47 checks passed
@vsanthanam vsanthanam deleted the vsanthanam/update-benchmarks branch January 16, 2026 23:37
@vsanthanam vsanthanam linked an issue Jan 17, 2026 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Instrument benchmark updates

1 participant