Bug #17025: `Time#ceil` does not work like `Rational#ceil` or `Float#ceil`

• Status: Closed
• Assignee: -
• Target version: -
• ruby -v: ruby 2.7.1p83 (2020-03-31 revision a0c7c23c9c) [x86_64-linux]
• Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN

[tgxworld (Guo Xiang Tan)]

Current behavior

irb(main):011:0> time = Time.utc(2016, 4, 23, 0, 0, "0.123456789".to_r)
irb(main):012:0> time.ceil(9)
=> 2016-04-23 00:00:00.12345679 UTC
irb(main):013:0> time.ceil(10)
=> 2016-04-23 00:00:00 1234567891/10000000000 UTC
irb(main):014:0> time.ceil(11)
=> 2016-04-23 00:00:00 12345678901/100000000000 UTC

irb(main):015:0> "0.123456789".to_r.ceil(9)
=> (123456789/1000000000)

irb(main):016:0> "0.123456789".to_f.ceil(9)
=> 0.123456789

Expected Behavior

irb(main):011:0> time = Time.utc(2016, 4, 23, 0, 0, "0.123456789".to_r)
irb(main):012:0> time.ceil(9)
=> 2016-04-23 00:00:00.123456789 UTC
irb(main):012:0> time.ceil(10)
=> 2016-04-23 00:00:00.123456789 UTC
irb(main):012:0> time.ceil(11)
=> 2016-04-23 00:00:00.123456789 UTC

[jeremyevans0 (Jeremy Evans)]

• Related to Feature #16470: Issue with nanoseconds in Time#inspect added

[jeremyevans0 (Jeremy Evans)]

I've added a pull request to fix this: https://github.com/ruby/ruby/pull/3362

• Status changed from Open to Closed

Applied in changeset git|520a734ad9c7348f4e4858ee24640f42c88fd389.

---

Fix Time#ceil when result should be the same as the receiver

Fixes [Bug #17025]

[tgxworld (Guo Xiang Tan)]

Thank you for fixing this Jeremy.