OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
pacman-aur low occasional DISPUTE

Get past an AUR build that fails in its check() test suite

archomarchyendeavouroscachyosdesktoplaptop
AUDITED Audited against its sources and confirmed accurate. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

/etc/makepkg.conf line 72 on this machine is BUILDENV=(!distcc color !ccache check !sign), as the cause quotes, and /etc/makepkg.conf.d holds only fortran.conf and rust.conf, so nothing overrides it. makepkg(8) defines --nocheck as 'Do not run the check() function in the PKGBUILD or handle the checkdepends'. makepkg.conf(5) gives $XDG_CONFIG_HOME/pacman/makepkg.conf and ~/.makepkg.conf as per-user overrides read after the system file. yay.8 documents --mflags. yay's parseLongOption in pkg/settings/parser/parser.go consumes the next argument for options that take a parameter, so yay -S <pkg> --mflags --nocheck passes --nocheck through. The Omarchy branch matches /usr/share/omarchy/bin/omarchy-update-aur-pkgs on 4.0.4-1, which runs yay -Sua --noconfirm --cleanafter --ignore gcc14,gcc14-libs with no makepkg flags. The danger is proportionate and steers toward the per-package flag. Not exercised: no AUR build was run.

RISK

Skipping tests means installing a build whose own test suite failed. If the failures are in core functionality rather than network or environment tests, the package may really be broken, so read the output before reaching for --nocheck, and prefer the per-package flag over disabling check globally.

Symptom

Compilation finishes, then the build stops while running the package's tests:


==> Starting check()...
...
FAILED: 2 of 431 tests
==> ERROR: A failure occurred in check().
    Aborting...
 -> error making: <pkgname>

The package itself would probably work. During omarchy update the AUR step fails on that one package and it stays at the old version.

Cause

makepkg runs a PKGBUILD's check() function after build() whenever the check option is enabled in BUILDENV, and it is enabled by default (BUILDENV=(!distcc color !ccache check !sign) in /etc/makepkg.conf on Omarchy 4.0.4-1). Test suites in AUR packages often fail for reasons unrelated to the built binary: tests that need network access, a display, a specific locale or timezone, more file descriptors, or tests that broke against a newer library before the maintainer updated the PKGBUILD. A non-zero exit from check() aborts the build.

Fix

Read the failing tests first. If they are network, sandbox or flaky timing failures, skip the test stage for this one build. --nocheck tells makepkg not to run check() or handle checkdepends, and yay passes it through with --mflags:


yay -S <pkgname> --mflags --nocheck

With makepkg directly:


makepkg -si --nocheck

Report the failure on the package's AUR page comments with the test output, so the maintainer can fix or disable the test.

To skip tests for all your AUR builds instead, disable the option in your user config, copying your system BUILDENV and changing only check:


mkdir -p ~/.config/pacman
grep -E '^BUILDENV=' /etc/makepkg.conf
echo 'BUILDENV=(!distcc color !ccache !check !sign)' >> ~/.config/pacman/makepkg.conf

Omarchy 4: omarchy update runs yay -Sua with no extra flags, so a package that fails check() fails there every time until you either build it once with --nocheck as above or set !check in the user config.

Verify

pacman -Q <pkgname> shows the new version and the next omarchy update (or yay -Sua) no longer reports error making: <pkgname>.

Sources

aur-build-fails-in-check-function