I'm confident this is unrelated to optmatch the R project, and it's possible this is no-action on our part while waiting for a fix from Travis, but documenting it here anyways since its hitting others, e.g. @benthestatistician in #127 .
It seems that the automated Travis jobs are failing when all three (oldrel, release, dev) are run simultaneously. It manifests generally as oldrel passing, then release and dev failing with a timing out error (no output for 10 minutes).
If you restart the release and dev jobs manually, they pass fine.
I'm confident this is unrelated to optmatch the R project, and it's possible this is no-action on our part while waiting for a fix from Travis, but documenting it here anyways since its hitting others, e.g. @benthestatistician in #127 .
It seems that the automated Travis jobs are failing when all three (oldrel, release, dev) are run simultaneously. It manifests generally as oldrel passing, then release and dev failing with a timing out error (no output for 10 minutes).
If you restart the release and dev jobs manually, they pass fine.
It's possible it's a config issue on our end, but I don't see a solution. There's some discussion on the travis-ci site (https://docs.travis-ci.com/user/common-build-problems/#My-builds-are-timing-out), but that is more in reference to a single slow job, rather than this parallel issue.