Skip to content

Enforce coverage thresholds in CI#1652

Merged
oferchen merged 1 commit into
masterfrom
prepare-for-production-release
Oct 30, 2025
Merged

Enforce coverage thresholds in CI#1652
oferchen merged 1 commit into
masterfrom
prepare-for-production-release

Conversation

@oferchen
Copy link
Copy Markdown
Owner

Summary

  • require cargo llvm-cov to fail if coverage drops below 95% for lines or functions
  • update the workflow step name to reflect the enforced threshold

Testing

  • not run (workflow change only)

https://chatgpt.com/codex/tasks/task_e_6902e135e73883238274dd3ad797474a

@oferchen oferchen merged commit 08b56dc into master Oct 30, 2025
@oferchen oferchen deleted the prepare-for-production-release branch October 30, 2025 09:47
oferchen added a commit that referenced this pull request May 5, 2026
Static, code-grounded audit of the fast_io fallback on macOS compared
to the Linux io_uring path and the post-#1868 Windows IOCP path.
Inventories every public copy/write/probe entry point with file:LINE,
documents the inferred per-file syscall budget, identifies which
io_uring features have no macOS analogue, and ranks the near-term
mitigations (#1657 pwritev+F_NOCACHE, #1385 kqueue backend, macOS
sendfile arm) by inferred payoff per unit of effort.
oferchen added a commit that referenced this pull request May 7, 2026
)

Document the macOS-specific code paths in crates/fast_io/src/, contrast
them against the Linux io_uring/copy_file_range/sendfile fast paths,
quantify the structural performance gap on small-file vs large-file
workloads, point at where dispatch_io and kqueue would close it, and
recommend cross-platform micro-benchmarks.

Refs #1652.
oferchen added a commit that referenced this pull request May 7, 2026
…3892)

Static audit of the macOS dispatch chain in crates/fast_io/, contrasted
against the Linux io_uring build, with bottleneck analysis and pointers
to the dispatch_io and async writer trait follow-ups.
oferchen added a commit that referenced this pull request May 13, 2026
Static, source-grounded audit of the macOS fallback chain in
crates/fast_io/. Maps each Linux io_uring path to its macOS
equivalent, identifies that MacosWriter (F_NOCACHE + writev) is
implemented but unwired from the disk-commit dispatcher, and
recommends a one-screen fix in disk_commit/process.rs to deliver
the win.
oferchen added a commit that referenced this pull request May 18, 2026
Static, code-grounded audit of the fast_io fallback on macOS compared
to the Linux io_uring path and the post-#1868 Windows IOCP path.
Inventories every public copy/write/probe entry point with file:LINE,
documents the inferred per-file syscall budget, identifies which
io_uring features have no macOS analogue, and ranks the near-term
mitigations (#1657 pwritev+F_NOCACHE, #1385 kqueue backend, macOS
sendfile arm) by inferred payoff per unit of effort.
oferchen added a commit that referenced this pull request May 18, 2026
)

Document the macOS-specific code paths in crates/fast_io/src/, contrast
them against the Linux io_uring/copy_file_range/sendfile fast paths,
quantify the structural performance gap on small-file vs large-file
workloads, point at where dispatch_io and kqueue would close it, and
recommend cross-platform micro-benchmarks.

Refs #1652.
oferchen added a commit that referenced this pull request May 18, 2026
…3892)

Static audit of the macOS dispatch chain in crates/fast_io/, contrasted
against the Linux io_uring build, with bottleneck analysis and pointers
to the dispatch_io and async writer trait follow-ups.
oferchen added a commit that referenced this pull request May 18, 2026
Static, source-grounded audit of the macOS fallback chain in
crates/fast_io/. Maps each Linux io_uring path to its macOS
equivalent, identifies that MacosWriter (F_NOCACHE + writev) is
implemented but unwired from the disk-commit dispatcher, and
recommends a one-screen fix in disk_commit/process.rs to deliver
the win.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant