git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 0/4] make linux32 ci job work with recent actions

From
Jeff King <peff@peff.net>
Date
Sep 12, 2024, 09:42 UTC
Message-ID
<20240912094238.GA589050@coredump.intra.peff.net>
In-Reply-To
<20240912080011.GA556677@coredump.intra.peff.net>
On Thu, Sep 12, 2024 at 04:00:11AM -0400, Jeff King wrote:
Show 5 quoted lines
> But I _think_ all of those details I sent add up to a possible patch
> series. But it probably still makes sense to take your patch here, as it
> unblocks CI in the short term. And then I can build the bigger fix on
> top of that (it touches the same spot, but in the end both end up
> removing that special case).

OK, here's what I came up with. I built it on top of what you have queued in jc/ci-upload-artifact-and-linux32, but it could be applied separately (and it should merge OK).

The state after each patch should still pass, but of course each of them depends on the ones before.

The big downside is discussed in patch 3: we are losing what is probably the oldest platform we test against. I don't think it's fixable in this approach, though; the Actions node just won't run on such an old platform. So the options are:

  - hope that they eventually move to a true static node binary
  - switch the design entirely; handle docker ourselves, run the actions
    in the regular runner-image environment, and then just do the "make
    test" bits inside the container

IMHO what's in this series is an OK tradeoff (we are going from an 8-year-old image to a 4-year-old one, but it gets older with each passing year). If somebody wants to pursue the alternate design above, be my guest. I'm just trying not to fall into that rabbit hole myself. ;)

  [1/4]: ci: drop run-docker scripts
  [2/4]: ci: unify ubuntu and ubuntu32 dependencies
  [3/4]: ci: use more recent linux32 image
  [4/4]: ci: use regular action versions for linux32 job
 .github/workflows/main.yml | 12 +++----
 ci/install-dependencies.sh | 45 +++++++++++++++-----------
 ci/run-docker-build.sh     | 66 --------------------------------------
 ci/run-docker.sh           | 47 ---------------------------
 4 files changed, 32 insertions(+), 138 deletions(-)
 delete mode 100755 ci/run-docker-build.sh
 delete mode 100755 ci/run-docker.sh
-Peff
Previous: Jeff KingNext: Jeff King
Message 5 of 24 in “ci: remove 'Upload failed tests' directories' step from linux32 jobs”
  1. ci: remove 'Upload failed tests' directories' step from linux32 jobsJunio C Hamano, Sep 9, 2024
  2. Junio C HamanoSep 11, 2024
  3. Jeff KingSep 12, 2024
  4. Jeff KingSep 12, 2024
  5. 0/4 make linux32 ci job work with recent actionsJeff King, Sep 12, 2024
  6. 1/4 ci: drop run-docker scriptsJeff King, Sep 12, 2024
  7. Patrick SteinhardtSep 12, 2024
  8. 2/4 ci: unify ubuntu and ubuntu32 dependenciesJeff King, Sep 12, 2024
  9. Patrick SteinhardtSep 12, 2024
  10. 3/4 ci: use more recent linux32 imageJeff King, Sep 12, 2024
  11. Patrick SteinhardtSep 12, 2024
  12. Jeff KingSep 12, 2024
  13. Patrick SteinhardtSep 12, 2024
  14. Patrick SteinhardtSep 12, 2024
  15. Jeff KingSep 13, 2024
  16. Patrick SteinhardtSep 13, 2024
  17. 4/4 ci: use regular action versions for linux32 jobJeff King, Sep 12, 2024
  18. Junio C HamanoSep 12, 2024
  19. 5/4 ci: add Ubuntu 16.04 job to GitLab CIPatrick Steinhardt, Sep 13, 2024
  20. Jeff KingSep 13, 2024
  21. Patrick SteinhardtSep 13, 2024
  22. Jeff KingSep 13, 2024
  23. Patrick SteinhardtSep 13, 2024
  24. Junio C HamanoSep 13, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.