Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DateTime method .earlier thinks that the time is flowing backwards (DateTime.now.earlier(years => 15)) #4993

Closed
p6rt opened this issue Jan 5, 2016 · 5 comments

Comments

@p6rt
Copy link

p6rt commented Jan 5, 2016

Migrated from rt.perl.org#127160 (status was 'resolved')

Searchable as RT127160$

@p6rt
Copy link
Author

p6rt commented Jan 5, 2016

From @AlexDaniel

Code​:
say DateTime.now.earlier(years => 15)

Result​:
2031-01-05T01​:57​:22.872850+01​:00

It is a regression, it was working just fine earlier.

It seems like there are no tests for this particular case (.earlier with
days, months, etc. seems to be fine).

@p6rt
Copy link
Author

p6rt commented Jan 5, 2016

From @lizmat

On 05 Jan 2016, at 02​:06, Alex Jakimenko (via RT) <perl6-bugs-followup@​perl.org> wrote​:

# New Ticket Created by Alex Jakimenko
# Please include the string​: [perl #​127160]
# in the subject line of all future correspondence about this issue.
# <URL​: https://rt-archive.perl.org/perl6/Ticket/Display.html?id=127160 >

Code​:
say DateTime.now.earlier(years => 15)

Result​:
2031-01-05T01​:57​:22.872850+01​:00

It is a regression, it was working just fine earlier.

It seems like there are no tests for this particular case (.earlier with
days, months, etc. seems to be fine).

Fixed with 18957e3f98e7830eb0c , tests added with afe667b , can be closed

Liz

@p6rt
Copy link
Author

p6rt commented Jan 5, 2016

The RT System itself - Status changed from 'new' to 'open'

@p6rt
Copy link
Author

p6rt commented Jan 9, 2016

From @usev6

On Tue Jan 05 01​:28​:09 2016, elizabeth wrote​:
[...]

Fixed with 18957e3f98e7830eb0c , tests added with afe667b , can be
closed

Thanks! I'm closing this ticket as 'resolved'.

@p6rt p6rt closed this as completed Jan 9, 2016
@p6rt
Copy link
Author

p6rt commented Jan 9, 2016

@usev6 - Status changed from 'open' to 'resolved'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant