| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| disable-test_security_curve.patch | disable test_security_curve It hangs in buildds that not x86/x64 based. | Laszlo Boszormenyi (GCS) <gcs@debian.org> | no | 2017-12-13 | ||
| tests_testutil.cpp.patch | =================================================================== | no | ||||
| test_hwm_pubsub-tcp-fix.patch | Fix flaky test_hwm_pubsub on riscv64 The failure has occasionally been seen on other architectures too, but shows up very frequently on riscv64, particularly in qemu, so is likely timing-dependent. . Upstream has been investigating the flakiness for years, but don't have a perfect fix. The rejected upstream PR this was ported from apparently fails on Windows, but we don't care about that. |
somdoron <somdoron@gmail.com> | no | https://github.com/zeromq/libzmq/pull/3462 | ||
| fix-maybe-uninitialized.patch | no | |||||
| fix_message_can_not_be_received_due_to_signal.patch | [PATCH] Problem: message can't be received due to signal Issue caught in Golang runtime, which widely uses signal SIGURG for scheduling. Sometimes messages cannot be received. Technically socket_base_t::process_commands() returns failure even if some commands were processed, but next message from mailbox could not be received during interrupt. |
Ilya Kondrashkin <ikondrashkin@nfware.com> | no | 2023-01-10 | ||
| fix-riscv64-build.patch | [PATCH] fix: fix build on qemu-user In qemu-user, CACHELINE_SIZE probe is undefined |
Han Gao <gaohan@iscas.ac.cn> | no | 2023-01-10 |