Merged #2218 into master.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2218#event-7803500644
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint maili
@pmatilai pushed 1 commit.
36ac15cbe724e87b8331cd5b338121c7bd0412be Enable malloc checking with random
perturb in the test-suite
--
View it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2218/files/5c6651663b46cd02c8be1817f0f42961a262cf94..36ac15cbe724e87b8331cd5b338121c7bd0412
OTOH I kinda wonder whether this should be done in the CI build instead. Wiring
these sort of things into the default build tends to bite back at some point.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2218#issuecomment-1266943826
You
Glibc provides low-cost memory sanity checking on it's own, it'd be
foolish not to take advantage of this in the test-suite for our CI. As this
introduces a level of randomness to the system, record the environment in a
file (in particular, glibc.malloc.perturb value) to make possible failures
