- This should avoid something like #16750 to occur
- this would require pacdb to be installed but it can be run
without having it installed for "checking whether to run".
For running the actual checks, pacdb is required.
- `pkgbase` is used to find the path to PKGBUILD for a given
package.
- The db which contains the files of packages is used by default.
files db is a superset of normal db, so using that should work.
I've never found it particular helpful and usually just ignored it.
One could argue that it could be improved to do what we want, but
I personally don't want to write that in bash.
It defaults to 1.8GB, bump it a bit so we can build
flang under clang64 which otherwise hits OOM
Use C: since we have 95GB free there and only 12GB on D:
Not an issue on fresh hosted runners, but on a re-used self-hosted
runner ntldd may already be installed. It's only mildly annoying having
it reinstalled every run, but easy enough to fix.
In case something crashes in CI this will show us some
information on which program crashed and why.
We register procdump as a JIT debugger which dumps the process
memory into a new file if triggered. To enable the JIT debugger
in the context of cygwin we need to set MSYS=winjitdebug.
The resulting dump file can for example be analyzed with
minidump-stackwalk or minidump_stackwalk
This will allow me to label runners according to whether I want them to
run autobuild or CI jobs (or both, theoretically).
See also msys2/msys2-autobuild#56
We don't upload them because they can get too large for GitHub.
Also their code path is mostly a subset of the real build,
so it doesn't add much for testing.
This way we don't have to install the VCS group.
See https://github.com/msys2/MINGW-packages/discussions/10506
This is an intermediate step. It results in CI installing fewer packages
by default before building, but makepkg-mingw will not complain since
it only checks for the C compiler when checking for the group.
If this works out we can update the docs and remove the install alltogether.
1- Sometimes a single PKGBUILD produce many packages, which make it not possible to remove an earlier (alphabetically) package before its dependent package. and that package will stay installed.
2- Ensure that the toolchain is installed in case the previous package is a part of it and get removed.
