Hi @XavierCLL,
As per the wiki:
check()
Place for calls to make check and similar testing routines. It is highly recommended to have check() as it helps to make sure software has been built correctly and works fine with its dependencies.
Users who do not need it (and occasionally maintainers who can not fix a package for this to pass) can disable it using BUILDENV+=('!check') in PKGBUILD/makepkg.conf or call makepkg with --nocheck flag.
I have disabled a few image comparison tests which always seem to fail. The rest pass for me, on two different computers and in a clean chroot. At some point I would like to find a more reliable arrangement to allow these image comparisons to pass but I am not sure how straightforward that would be as the failures are often very small shifts in position rather than real errors.
In the meantime, I think the remaining ~650 tests are a useful check of the package's behaviour. You can edit /etc/makepkg.conf
or use makepkg --nocheck
as stated above if you wish to skip the checks on your machine (if you use an AUR helper, see if they have an equivalent option; yay uses --mflags
to pass options to makepkg so you could use yay --mflags --nocheck -S python-cartopy
for example).
Pinned Comments
bcb commented on 2023-12-08 10:48 (UTC)
The currently enabled tests pass (repeatedly) for me in a clean chroot. I am reluctant to disable too many tests in the PKGBUILD, especially when I cannot reproduce the failures and make sure I am disabling the correct test for a build failure reported by somebody else. For now, if you run into failures you may have to build with
--nocheck
. I am hoping to make the checks more robust -- suggestions welcome!