diff options
author | 0xb10c <b10c@b10c.me> | 2022-11-28 21:26:26 +0100 |
---|---|---|
committer | 0xb10c <b10c@b10c.me> | 2022-11-28 21:26:26 +0100 |
commit | 2811f40f3099a22091870d6aa2efecd741d186ce (patch) | |
tree | 1034733d6901d85d5b31fd754bc7d4aed5bcabc0 /test/functional/interface_bitcoin_cli.py | |
parent | a79b720092b6ce4134d386e95b3473a290f3c127 (diff) |
ci: only run USDT interface tests on CirrusCI
As mentioned in #26571, the task running the USDT interface tests
fail when run in docker. cc7335edc87c6ef34429b4df94f53973db520aac
in #25528 added that the tests are run in a **VM** in Cirrus CI.
Running them locally in docker containers might not work:
- We use [bcc] as tracing toolkit which requires the kernel headers
to compile the BPF bytecode. As docker containers use the hosts
kernel and don't run their own, there is a potential for mismatches
between kernel headers available in the container and the host
kernel. This results in a failure loading the BPF byte code.
- Privilges are required to load the BPF byte code into the kernel.
Normally, the docker containers aren't run with these.
- We currently use an untrusted third-party PPA to install the
bpfcc-tools package on Ubuntu 22.04. Using this on a local dev
system could be a security risk.
To not hinder the ASan + LSan + UBSan part of the CI task, the USDT
tests are disabled on non-CirrusCI runs.
[bcc]: https://github.com/iovisor/bcc
Diffstat (limited to 'test/functional/interface_bitcoin_cli.py')
0 files changed, 0 insertions, 0 deletions