test: verify CI behavior for conflicting PR#14776
Conversation
3e26a29 to
62541ab
Compare
|
📝 Benchmark detail: Open
Base persistent cache hit rate: 👍 Current persistent cache hit rate: 👍 |
📦 Binary Size-limit
⏳ The base commit triggered a linux binding build, but its binary size data has not been generated yet, so the size comparison is skipped. Please re-run this workflow once the ecosystem-benchmark data for that commit is published. Warning Reference only — not the real baseline. The base commit's data isn't ready yet, so this compares against the nearest earlier commit that has data ( 🙈 Size remains the same at 66.53MB |
Merging this PR will improve performance by 3.85%
|
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ⚡ | Simulation | rust@create_concatenate_module |
15 ms | 14.5 ms | +3.85% |
Tip
Curious why this is faster? Comment @codspeedbot explain why this is faster on this PR, or directly use the CodSpeed MCP with your agent.
Comparing fy/conflict-pr-demo (3e26a29) with main (10840b8)
Footnotes
-
47 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩
Summary
main.pull_requestsynchronizeevent when the PR has a merge conflict.Related links
Validation
git diff --checkpasses and the PR is mergeable.git merge-tree --write-tree HEAD origin/mainreports a content conflict incrates/rspack_plugin_esm_library/src/link.rs.Checklist