-
Notifications
You must be signed in to change notification settings - Fork 355
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TRIVIAL] Disable 3.16 scenario in CI #978
Conversation
b8ba5ca
to
b1338cb
Compare
b1338cb
to
4c20684
Compare
Wow, even 10 minutes isn't enough time for 3.16 😬 - I'm going to try 15 minutes and then see how long they actually take to finish to see if that's excessive |
Of course with 15 minutes of room it finishes in 8m 🤷♂️ |
After discussion with @mixonic, we've decided to not run the 3.16 scenario in CI since it's the most inconsistent (but consistently slow) scenario. We'll leave it in the ember-try config for now until we officially drop support. |
Co-authored-by: Matthew Beale <matt.beale@addepar.com>
The Ember 3.12 and 3.16 tests don't reliably finish in under 7 minutes. This is currently blocking merge of #976 because the 3.16 tests need more time to run (a re-run of 3.12 did manage to finish in just under the timeout).
This PR bumps the GitHub Actions CI timeout from 7 minutes to 10 minutes.This PR disables the 3.16 scenario in CI since it's the slowest and most inconsistent scenario. It remains configured in ember-try should we need to debug any reported issues, but we will likely drop support for 3.12 and 3.16 altogether in the near future.