Skip to content

Commit 233822d

Browse files
committed
Merge #1195: ctime_tests: improve output when CHECKMEM_RUNNING is not defined
8f51229 ctime_tests: improve output when CHECKMEM_RUNNING is not defined (Jonas Nick) Pull request description: When seeing the output ``` Unless compiled under msan, this test can only usefully be run inside valgrind. ``` I thought that I would have to go back to the `configure` output to manually check if it was compiled under memsan to determine whether this test can be usefully run outside valgrind. But when we go into this branch then it was definitely not compiled under msan, which means that we can make the output clearer. ACKs for top commit: sipa: utACK 8f51229 real-or-random: utACK 8f51229 Tree-SHA512: a4953a158b1375d8fc3a2ee29e7014c5399becf5f75ffd3765c0141861e092fbc120003e00dfd25ec54b92a466e133377b96d5a9f4017c100aaf64fb9a045df1
2 parents ad7433b + 8f51229 commit 233822d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/ctime_tests.c

+1-1
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ int main(void) {
3838
int ret, i;
3939

4040
if (!SECP256K1_CHECKMEM_RUNNING()) {
41-
fprintf(stderr, "Unless compiled under msan, this test can only usefully be run inside valgrind.\n");
41+
fprintf(stderr, "This test can only usefully be run inside valgrind because it was not compiled under msan.\n");
4242
fprintf(stderr, "Usage: libtool --mode=execute valgrind ./ctime_tests\n");
4343
return 1;
4444
}

0 commit comments

Comments
 (0)