Closed SethTisue closed 3 years ago
Travis ran on https://github.com/scala/scala/pull/9783
https://app.travis-ci.com/github/scala/scala/requests shows "could not parse" for 2.13.x
🤦 — I'll fix it after breakfast
scala/scala@548c776deb42bc545296a1469291777a16e0b3cf
https://app.travis-ci.com/github/scala/scala/builds/239656900
👍
It didn't run on https://github.com/scala/scala/pull/9697 , which is a PR we actually need it on (since Jenkins doesn't do the Dotty check)
And we don't have a cron run to show us whether https://github.com/scala/scala-dev/issues/791 is fixed
Lukas and I had talked about maybe eliminating Travis-CI from PR validation (since it's largely redundant with Jenkins, and since we only have a one-job-at-a-time plan, so it's a potential bottleneck), maybe now's the time for that, but regardless, we need Travis-CI to be working in order to do releases, and the cron job either needs to be running or be moved to GitHub Actions.
The broader discussion on the whole situation is https://github.com/scala/scala-dev/issues/751 , but I made this separate ticket because we need to do something short term, even if doesn't involve longer term changes