sm64-port built using mingw-w64 GCC (MSYS2) under Github Actions won't run, exit code 132

Question

Update: I believed this happened due issues with upload-artifact action, namely, corrupted ZIP when downloading the artifact, as many issues addressed that (and apparently persist today).

However, after building again and again, and after adding a checksum to the workflow, checksum differs between builds, producing the following checksums (in chronological order, newest to oldest):

• ❌025e1095d37a97776d2d03cb42772321c3bdc9c1 *build/us_pc/sm64.us.exe [logs]
• ✅04a3a25320a7dc49dc6c8fda823fff1e5e3308e3 *build/us_pc/sm64.us.exe [logs]
• ❌44b3a4c033d06bbce31e8d8f41be74dcc275b465 *build/us_pc/sm64.us.exe [logs]
• ✅0fbe7aa5ceae9758ea04355a04432aae160bf537 *build/us_pc/sm64.us.exe [logs]
• ❌3720a2fc1e37d38d4afb6799c07ce2b7fb530c4a *build/us_pc/sm64.us.exe [logs]

Checksum matches for the ones produced by the workflow, the files uploaded to Artifacts, and those ones uploaded to Google Drive, so, it is not a ZIP corruption.

I have adopted the Super Mario 64 port project to create Docker images with the tools and dependencies to successfully build usable executables for Linux (GCC 13) and Windows (MinGW-w64 GCC).

I attepted to build Windows executables using mingw-w64-x86_64-gcc (and its dependendencies) under the following Windows-based environments:

• MSYS2 installed directly to a fresh Windows Server 2022 installation at Google Cloud using the GUI-based MSYS2 installer downloaded from the official website, then, install mingw-w64-x86_64-gcc and dependencies from the command line: builds and runs [GDB output]

• My Docker container (basically the same as above, but MSYS2 installed using Chocolatey): builds and runs

• GitHub Actions using this workflow (relevant logs) that uses the built-in MSYS2 environment: build failed due missing hexdump

• GitHub Actions using this workflow that uses msys2/setup-msys2 to install a separated MSYS2 environment and dependencies in an attemp to solve the missing dependencies on the built-in MSYS2 env: builds but fails to run (no window, then process ended) [Actions logs] [GDB output]

Is there I missed? Us there a way to install hexdump (util-linux) into the built-in MSYS2 environment?

I already finded further missing dependencies but the executable built in GitHub Actions platform is still unreproducible. Please note I'm not a developer, just a hobbist. Thanks in advance.