You are not logged in.
My llvm trunk packages* do build tests and have a check() function , but the tests fail rather often.
In order to be able to run the tests in check() , -D LLVM_BUILD_TESTS=ON \ is used to instruct cmake/ninja to build tests.
This increases the time & resources needed during build() by a lot.
If there is a way to determine whether makepkg is run with --nocheck (or !check in BUILDENV ) , I could disable building tests for that case and get a substantial speedup .
How could this be achieved ?
*
f.e. https://aur.archlinux.org/packages/llvm-minimal-git
Last edited by Lone_Wolf (2020-03-20 12:53:32)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Is there no way to make cmake only build the test code during "ninja check" rather than by default during build()?
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
I couldn't find an option for that, but decided to try anyway .
It turned out the check-* targets verify if build tests are already compiled and if not, compile them first and then run the tests.
So it seems the upstream developers had already considered this usecase.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Hmm, so you're saying LLVM_BUILD_TESTS doesn't configure whether the tests are added to the build system, but only configures whether they are built by default?
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
That's what it looks like to me.
In order to allow others to replicate results (without having to deal with everchanging vcs packages) , I've used extra-x86_64-build on llvm-9.0.1-2 from repos to build with -D LLVM_BUILD_TESTS=ON and OFF .
The logs are uploaded to my box account and shared for download/view .
-DLLVM_BUILD_TESTS=OFF
https://app.box.com/s/egq8cl70rmx4wwt9a5nt4mmpxj82hnds
https://app.box.com/s/7b5pty8l9kksakehocb8v48ndxn7rdp2
-DLLVM_BUILD_TESTS=ON
https://app.box.com/s/n9jkx0wtvs26kyrbyr4pdigvisshz95h
https://app.box.com/s/2nr8hdewtrhg7m0pi4mcn4usbtefk2t6
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline