CI: arm Travis build timing out

[jbrockmendel]

I'm seeing this in most but not all builds ATM.

Even if we moved it to allowed-failures, it would still be slowing the Travis turnaround time down a lot.

[jreback]

can we ping original implementer of arm support (i don't remember the github id)

also might be helpful to run this build more verbosely to see if can nail down where it's hanging

[TomAugspurger]

cc @janaknat from MacPython/pandas-wheels#99 and @odidev from the original issue.

Here's an example timeout: https://travis-ci.org/github/pandas-dev/pandas/jobs/731231340

[janaknat]

@TomAugspurger @jreback It would help if pandas-dev migrated to travis-ci.com from travis-ci.org.

I did a test run on travis-ci.com using Graviton2: https://travis-ci.com/github/janaknat/pandas/jobs/392535745

travis-ci.com offers Graviton2 instances for building/testing in an ARM64 environment. That will speed things up significantly.
See: https://blog.travis-ci.com/2020-09-11-arm-on-aws

[odidev]

I have tested this again and there is inconsistency in build timings in arm64 for each build. So, I have tested with arm64-graviton2 in travis-ci.com, and build ran in 25 mins(almost similar to AMD64).

ARM64-Graviton2 build report: https://travis-ci.com/github/odidev/pandas/jobs/392555700

[jbrockmendel]

Disable until this is sorted out?

[jreback]

@TomAugspurger @jreback It would help if pandas-dev migrated to travis-ci.com from travis-ci.org.

I did a test run on travis-ci.com using Graviton2: https://travis-ci.com/github/janaknat/pandas/jobs/392535745

travis-ci.com offers Graviton2 instances for building/testing in an ARM64 environment. That will speed things up significantly.
See: https://blog.travis-ci.com/2020-09-11-arm-on-aws

I don't think we have an objection to migrate (and seems we need to)

what do we need to do?

[janaknat]

@jreback documentation for migrating repos: https://docs.travis-ci.com/user/migrate/open-source-repository-migration. It shouldn't be too much of a hassle.

@mattip has done that for the Macpython/scipy-wheels repo.

@mustafa-travisci and @michal-at-travisci can help with more information.

[mattip]

I can do the legwork to migrate the repo (under my alias @multibuilder) if the core maintainers sign off on the idea. This would mean they would now need to sign into travis-ci.com rather than travis-ci.org or ask me in order to manage the build settings: set secrets, stop/start specific builds. Automatic triggering would work as before. We recently migrated the scipy-wheel build to travis-ci.com, so this second migration should be easier.