diff options
| author | MarcoFalke <*~=`'#}+{/-|&$^_@721217.xyz> | 2022-12-02 10:52:43 +0100 |
|---|---|---|
| committer | MarcoFalke <*~=`'#}+{/-|&$^_@721217.xyz> | 2022-12-02 10:52:52 +0100 |
| commit | 9e59d21fbe5746b220f35b0a5a735198c3e6dcdb (patch) | |
| tree | b06f930a3baaf54c66c2db4b5506154266e51cef /depends | |
| parent | 4037478114d4b3e4824ac200dcd569890dbf9544 (diff) | |
| parent | 2811f40f3099a22091870d6aa2efecd741d186ce (diff) | |
| download | bitcoin-9e59d21fbe5746b220f35b0a5a735198c3e6dcdb.tar.xz | |
Merge bitcoin/bitcoin#26592: ci: only run USDT interface tests on CirrusCI
2811f40f3099a22091870d6aa2efecd741d186ce ci: only run USDT interface tests on CirrusCI (0xb10c)
Pull request description:
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
Top commit has no ACKs.
Tree-SHA512: 7c159b59630b36d5ed927b501fa0ad6f54ff3d98d0902f975cc8122b4147a7f828175807d40a470a85f0f3b6eeb79307d3465a287dbd2f3d75b803769ad0b6e7
Diffstat (limited to 'depends')
0 files changed, 0 insertions, 0 deletions