BUG: Avoid undefined behaviour when converting from float to timedelta
Summation of timedelta series with NaTs in them result in undefined
behaviour because the final wrapping step of the summation ends up
converting the NaNs in the sum through a direct cast to int64.  This
cast is undefined for NaN and just happens to work on x86_64 because
of the way `cvttd2si` works.  On Aarch64, the corresponding `fcvtzs` sets
the result to 0 on undefined input.

This fix trivially sets the conversion target to m8 instead of i8 so
that numpy correctly casts from NaN to NaT.  Note that the fix in
numpy for the same is pending in PR numpy/numpy#14669 .

There is an existing test (test_sum_nanops_timedelta in
frame/test_analytics.py) that exercises this bug and has been verified
to have been fixed with this and the numpy patch.

- [ ] closes #xxxx
- [ ] tests added / passed
- [x] passes `black pandas`
- [x] passes `git diff upstream/master -u -- "*.py" | flake8 --diff`
- [ ] whatsnew entry

> There is an existing test (test_sum_nanops_timedelta in
frame/test_analytics.py) that exercises this bug and has been verified
to have been fixed with this and the numpy patch.

is there a test that would fail currently on our CI and pass with this patch? or is this just platform specific? cc @jbrockmendel  > > There is an existing test (test_sum_nanops_timedelta in
> > frame/test_analytics.py) that exercises this bug and has been verified
> > to have been fixed with this and the numpy patch.
> 
> is there a test that would fail currently on our CI and pass with this patch? or is this just platform specific?

It looks like all of your CI tests are x86-only, so you won't see this issue.  If you run the testsuite on aarch64 though, you'll see `test_sum_nanops_timedelta` fail without this patch and pass with it. > If you run the testsuite on aarch64 though

Do azure or travis offer such a thing?  (Or anyone else?) > > If you run the testsuite on aarch64 though
> 
> Do azure or travis offer such a thing? (Or anyone else?)

I believe Travis does now, as of just 4 days ago:

https://blog.travis-ci.com/2019-10-07-multi-cpu-architecture-support thanks @siddhesh 

would be interested in adding a travis build on arm? (can you open a separate issue to track).