Repository navigation
Conversation
|
I think we don't need to revert this since we were not running test(impossible?) for Redox on the CI previously. |
|
I think we should add a check-only job at the very least: cargo check --all-targets --features feat_os_unix_redox --target x86_64-unknown-redoxWe can set |
|
Sounds good |
This comment was marked as outdated.
This comment was marked as outdated.
|
Do we really need to hurry supporting test on redox? Most logic are shared with other platforms. |
d2139df to
e8df3ba
Compare
Merging this PR will regress 1 benchmark
|
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | Memory | du_deep_tree[(100, 3)] |
76.5 KB | 82.4 KB | -7.14% |
| ⚡ | CPU Simulation | true_consecutive_calls |
350.2 ns | 294.7 ns | +18.85% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing xtqqczze:GH14664 (f8a0e4b) with main (ae34722)2
Footnotes
-
70 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. ↩
-
No successful run was found on
main(198c615) during the generation of this report, so ae34722 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩
5787bfb to
5489611
Compare
|
If we replaced |
546552d to
d71ebe6
Compare
|
Split the |
|
|
Is there any collaborator for |
407f7d4 to
d861d13
Compare

Closes #14914.
Reverts #14664.