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

One of the CI checks failed so I closed and was going to work back through it but looking at the checks for recent commits to Master this might be a Travis issue so reopening.  Looks like the failure is trailing whitespace on line 1781 hmm thanks, fixed. Initially the check that failed was that Travis timed out while compiling. 

Is it normal for commits to master to be showing CI check fails? When i saw that, I assumed there was something going on and that I should just try again later.   > Is it normal for commits to master to be showing CI check fails? When i saw that, I assumed there was something going on and that I should just try again later.

We recently added a Travis build for python3.8 and it is timing out annoyingly often.  Just re-started that, so hopefully it will resolve itself. Great thanks @HughKelley 