An alternative would be to only run a cut down selection of tests with msan.
Pauli
--
Dr Paul Dale | Distinguished Architect | Cryptographic Foundations
Phone +61 7 3031 7217
Oracle Australia
> On 14 Feb 2020, at 11:00 pm, Matt Caswell wrote:
>
>
>
> On 14/02/2020 12:23, Nicola Tuveri
On Fri, 14 Feb 2020 at 14:00, Matt Caswell wrote:
>
> To be clear the build that is timing out uses *msan* not *asan*.
>
As I understand it msan detects unitialised reads. whereas asan detects
> memory corruption, buffer overflows, use-after-free bugs, and memory leaks.
>
> The previous
On 14/02/2020 12:23, Nicola Tuveri wrote:
> If ASAN is too slow to run in the CI should we restore the previous
> homemade checks for memory leaks as an alternative to be run in regular
> CI runs and leave ASAN builds to run-checker on the master branch only?
To be clear the build that is
If ASAN is too slow to run in the CI should we restore the previous
homemade checks for memory leaks as an alternative to be run in regular CI
runs and leave ASAN builds to run-checker on the master branch only?
Here is another idea that would be interesting if we restore the previous
checks:
I
