mirror of
https://github.com/bitcoin/bitcoin.git
synced 2025-02-23 07:15:29 +01:00
Our CI tasks are run by CirrusCI in Docker containers in a Google Compute Engine based Kubernetes environment. These containers have limited capabilities - especially CAP_SYS_ADMIN is missing. See https://github.com/bitcoin/bitcoin/issues/23296#issuecomment-1024920845 We need elevated privileges to hook into the USDT tracepoints. We use a CirrusCI "compute_engine_instance" (a VM, not a container) where we have the required privileges. The ubunut-mininmal-2204-lts was choosen with debian-11 being an alternative. Both pack an outdated 'bpfcc-tools' package (v0.18.0) from 2020. This version prints warnings to stderr during BPF bytecode compilation, which causes our functional test runner to fail. This is fixed in newer verison. Until debian-12 or a newer Ubuntu release is avaliable as image in GCE (https://cloud.google.com/compute/docs/images/os-details), we use a third-party and untrusted PPA that releases up-to-date versions of the package. The official iovisor (authors of BCC) PPA is outdated too. An alternative would be to compile BCC from source in the CI. Co-authored-by: MacroFake <falke.marco@gmail.com> |
||
---|---|---|
.. | ||
00_setup_env.sh | ||
00_setup_env_android.sh | ||
00_setup_env_arm.sh | ||
00_setup_env_i686_centos.sh | ||
00_setup_env_i686_multiprocess.sh | ||
00_setup_env_mac.sh | ||
00_setup_env_mac_native_x86_64.sh | ||
00_setup_env_native_asan.sh | ||
00_setup_env_native_fuzz.sh | ||
00_setup_env_native_fuzz_with_msan.sh | ||
00_setup_env_native_fuzz_with_valgrind.sh | ||
00_setup_env_native_msan.sh | ||
00_setup_env_native_nowallet_libbitcoinkernel.sh | ||
00_setup_env_native_qt5.sh | ||
00_setup_env_native_tidy.sh | ||
00_setup_env_native_tsan.sh | ||
00_setup_env_native_valgrind.sh | ||
00_setup_env_s390x.sh | ||
00_setup_env_win64.sh | ||
04_install.sh | ||
05_before_script.sh | ||
06_script_a.sh | ||
06_script_b.sh | ||
wrap-qemu.sh | ||
wrap-valgrind.sh | ||
wrap-wine.sh | ||
wrapped-cl.bat |