ci: use upload-artifacts v1 for dockerized jobs
commit3cf9bb36bf3ab826a7ea358132423ed2bf3bc7db
authorCarlo Marcelo Arenas Belón <carenas@gmail.com>
Fri, 13 Aug 2021 09:13:49 +0000 (13 02:13 -0700)
committerJunio C Hamano <gitster@pobox.com>
Sun, 15 Aug 2021 16:45:38 +0000 (15 09:45 -0700)
tree514cd77d107ddd81d38ad18e893332cd7518f133
parent5d213e46bb7b880238ff5ea3914e940a50ae9369
ci: use upload-artifacts v1 for dockerized jobs

e9f79acb28 (ci: upgrade to using actions/{up,down}load-artifacts v2,
2021-06-23) changed all calls to that action from v1 to v2, but there
is still an open bug[1] that affects all nodejs actions and prevents
its use in 32-bit linux (as used by the Linux32 container)

move all dockerized jobs to use v1 that was built in C# and therefore
doesn't have this problem, which will otherwise manifest with confusing
messages like:

  /usr/bin/docker exec  0285adacc4536b7cd962079c46f85fa05a71e66d7905b5e4b9b1a0e8b305722a sh -c "cat /etc/*release | grep ^ID"
  OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: no such file or directory: unknown

[1] https://github.com/actions/runner/issues/1011

Signed-off-by: Carlo Marcelo Arenas Belón <carenas@gmail.com>
Acked-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
.github/workflows/main.yml