selinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Iooss <nicolas.iooss@m4x.org>
To: selinux@vger.kernel.org
Subject: [PATCH 2/2] GitHub Actions: drop Ruby 2.4 from matrix
Date: Sun,  6 Dec 2020 23:56:25 +0100	[thread overview]
Message-ID: <20201206225625.3077530-2-nicolas.iooss@m4x.org> (raw)
In-Reply-To: <20201206225625.3077530-1-nicolas.iooss@m4x.org>

When migrating to Ubuntu 20.04, Ruby 2.4 is no longer available. As the
migration of "ubuntu-latest" to Ubuntu 20.04 is coming soon, according
to https://github.com/actions/virtual-environments/issues/1816, remove
it now.

Moreover the support of Ruby 2.4 ended a few months ago, so there is no
point at supporting bindings (and testing them) for this version:
https://www.ruby-lang.org/en/news/2020/04/05/support-of-ruby-2-4-has-ended/

Signed-off-by: Nicolas Iooss <nicolas.iooss@m4x.org>
---

I hit this on https://github.com/fishilico/selinux/runs/1507627386?check_suite_focus=true
and the fix is simple.
I would like to keep using ubuntu-latest image in order to benefit from
automatic "LTS upgrade" when they become available. I find it better
than having to update the Ubuntu version by hand (like was done for the
Travis-CI configuration), because maintainers do not have to remember
to update the configuration file for GitHub Actions.

If you prefer using fixed Ubuntu versions (or even several Ubuntu
versions!), the configuration can be modified accordingly.

 .github/workflows/run_tests.yml | 1 -
 1 file changed, 1 deletion(-)

diff --git a/.github/workflows/run_tests.yml b/.github/workflows/run_tests.yml
index d889b5d55604..ef4be8afc02f 100644
--- a/.github/workflows/run_tests.yml
+++ b/.github/workflows/run_tests.yml
@@ -24,7 +24,6 @@ jobs:
           # Test several Ruby versions with the latest Python version
           - {python: 3.9, ruby: 2.6}
           - {python: 3.9, ruby: 2.5}
-          - {python: 3.9, ruby: 2.4}
         exclude:
           - compiler: clang
             python-ruby-version: {python: 3.9, ruby: 2.7, other: linker-bfd}
-- 
2.29.2


  reply	other threads:[~2020-12-06 22:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-06 22:56 [PATCH 1/2] GitHub Actions: upgrade to Python 3.9 Nicolas Iooss
2020-12-06 22:56 ` Nicolas Iooss [this message]
2020-12-07 16:42   ` [PATCH 2/2] GitHub Actions: drop Ruby 2.4 from matrix William Roberts
2020-12-07 16:43 ` [PATCH 1/2] GitHub Actions: upgrade to Python 3.9 William Roberts
2020-12-09 21:43   ` Nicolas Iooss

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201206225625.3077530-2-nicolas.iooss@m4x.org \
    --to=nicolas.iooss@m4x.org \
    --cc=selinux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).