pika
pika copied to clipboard
pika builds on C++ std::execution with fiber, CUDA, HIP, and MPI support.
This is potentially very important for debugging. We currently only test with lsan (leak sanitizer). We should try to add tsan (thread sanitizer), msan (memory sanitizer), asan (address sanitizer), and...
Try to use the CSCS spack build cache in CI once #32 is done.
It may be useful to process events/requests according to priorities instead of submission order (or in addition to submission order).
#891 pushes performance data to elastic. We should expand this to push general metrics about the builds: - [x] test pass/fail (#907) - [x] test time (this gets us header...
Sometimes reported by address sanitizer, e.g. in the `thread_stacksize_current` test: ``` ================================================================= ==6427==ERROR: AddressSanitizer: stack-use-after-scope on address 0x7fdc770c2920 at pc 0x7fdc7f9cc7b4 bp 0x7fdc770c28d0 sp 0x7fdc770c28c8 WRITE of size 16 at...
Currently the address sanitizer CI job added in #972 explicitly disables `detect_stack_use_after_return` (default is also off, but this is to protect from a change to the default). It seems like...
Currently our custom signal handlers may allocate, which thread sanitizer reports as unsafe (since it may cause further signals). Check if we can somehow clean this up. However, this is...
Part of #926
It's unclear if these are false positives, or real. E.g. (in nearly any test using the pika schedulers, both `deque` and `MoodyCamel` queue): ``` WARNING: ThreadSanitizer: data race (pid=3631945) Atomic...
As reported by thread sanitizer (e.g. in `channel_mpsc_shift` test): ``` ================== WARNING: ThreadSanitizer: data race (pid=3631340) Read of size 4 at 0x7b04000028c0 by thread T1: #0 pika::experimental::base_channel_mpsc::get(int*) const /home/mjs/src/pika/libs/pika/synchronization/include/pika/synchronization/channel_mpsc.hpp:112 (channel_mpsc_shift_test+0x10fbb9)...