alternative to #27850
see #27850 (comment)
just testing ci for now
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline for information on the review process. A summary of reviews will appear here.
<!--174a7506f384e20aa4161008e828411d-->
Reviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
18 | @@ -19,7 +19,7 @@ export LSAN_OPTIONS="suppressions=${BASE_ROOT_DIR}/test/sanitizer_suppressions/l 19 | export TSAN_OPTIONS="suppressions=${BASE_ROOT_DIR}/test/sanitizer_suppressions/tsan:halt_on_error=1:log_path=${BASE_SCRATCH_DIR}/sanitizer-output/tsan" 20 | export UBSAN_OPTIONS="suppressions=${BASE_ROOT_DIR}/test/sanitizer_suppressions/ubsan:print_stacktrace=1:halt_on_error=1:report_error_type=1" 21 | if [[ $BITCOIN_CONFIG = *--with-sanitizers=*address* ]]; then # If ran with (ASan + LSan), Docker needs access to ptrace (https://github.com/google/sanitizers/issues/764) 22 | - CI_CONTAINER_CAP="--cap-add SYS_PTRACE" 23 | + CI_CONTAINER_CAP="--cap-add SYS_PTRACE --cap-add LINUX_IMMUTABLE"
This has nothing to do with asan, you will have to add it to all created containers.
I think you can just use the existing pull request to push the changes. It is clear that this approach will be working. Just pay attention to the details and make sure you are confident in your diff before you push, if possible.