stop testing easyconfig PRs with Travis, only use GitHub Actions from now on #11055
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The tests in Travis CI have been a PITA recently: next to the frequent fluke failures (which were mitigated through my bot fairly efficiently), we've also been hitting timeouts where the test suite doesn't generate any output for too long, causing Travis to cancel the test job.
We tried using
travis_wait
(cfr. #11008) to make Travis be more patient, but that doesn't seem to be enough, see for example:(from https://travis-ci.org/github/easybuilders/easybuild-easyconfigs/jobs/714454534)
Since we're only testing with Python 2.7 and 3.6 in Travis, there's nothing we're testing in Travis that is not also being tested in GitHub Actions.
So, I'm calling it: no more testing with Travis for easyconfig PRs, only GitHub Actions from now on!