Repository navigation
Fix some more issues with date - #15286
anastygnome wants to merge 5 commits into
Conversation
91c3d0d to
85d26e7
Compare
85d26e7 to
e7c1723
Compare
|
@xtqqczze but wait |
e7c1723 to
b15b029
Compare
b15b029 to
c445f8c
Compare
c445f8c to
9334d9d
Compare
9334d9d to
b23c91c
Compare
b23c91c to
0af1aad
Compare
546e653 to
4dcc800
Compare
22c87c3 to
b586575
Compare
Merging this PR will degrade performance by 3.45%
|
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ |
Simulation | single_date_now |
179.5 µs | 185.9 µs | -3.45% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing anastygnome:test-util (96328d7) with main (1747ba1)
Footnotes
-
460 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. ↩
Hmm @sylvestre, maybe this is too sensitive. |
b586575 to
c64e6e7
Compare
|
@SichenLiang Added a commit to fix the regression you spotted with %F |
c64e6e7 to
60df587
Compare
|
Thanks! checked 60df587, and the cases we reported now match GNU, including I found one case that went back to the behavior from before #15111: $ TZ=UTC LC_ALL=C date -d 2024-06-15 +%+6FGNU 9.12 and current main print |
The performance regression is consistent, but it's not a blocker. |
|
@anastygnome I'm obliged to ask: does this fix any open issues or supersede any PRs? Also, is it ready for review? |
60df587 to
1a1a9b3
Compare
fixed |
we found a regression (thanks @SichenLiang ) but it should be ready now! The fixed issues are in the commit messages. |
|
@anastygnome Could you move GitHub issue references from the commit message to the PR description instead? This makes issues easier to track and avoids spamming the issues with references to individual commits (e.g. #14681). |
@xtqqczze done |
Co-authored-by: Daniel Hofstetter <daniel.hofstetter@42dh.com>
1a1a9b3 to
96328d7
Compare
|
@anastygnome Does this PR supersede #14781 and #14791? |
What do you mean there's more? Of course,! |


Closes #14681
Closes #12943
Closes #14674
Closes #14679
Closes #14781
Closes #14791