CI: Adding CTest memcheck to CodeBuild

[boquan-fang]

Resolved issues:

Create another buildspec file for CTest memcheck. Following previous tickets instructions #3758 and PR#4369.

Description of changes:

• Add Valgrind check options for both regular and pedantic valgrind checks into the code base. The CTest memcheck should only triggers pedantic valgrind check if the libcrypto in used is openssl-1-1-1.
• Create a new codebuild spec file buildspec_valgrind.yml.
• Append some new valgrind suppressions to handle platform updates from Ubuntu18 to Ubuntu22.

Call-outs:

• Clang compiler is not included in this PR, because Ubuntu 18 and 22's Valgrind can't check clang-compiled executable. Update Valgrind version in CI docker image #4759
  • Need Valgrind version 20 or more to test Clang compiled executable.
• “cannot find memory tester output file” message are a result of logging valgrind errors through the --log-fd=2 option. I could not find another approach. Please see this comment for my reasoning.
• This is an example of how failed CTest memcheck codebuild looks like.
• For the scope of this PR, pedantic Valgrind check will still run on Ubuntu 18.
  • This is also tracked in this issue.
• backtrace function leaks a static amount of memory when it is first loaded, so it is safe to suppress. Read this explanation for further details.

Testing:

• Create a new CodeBuild job called Valgrind and use this PR as source. The CodeBuild job is successfully.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[boquan-fang]

Explanation for "cannot find memory tester output file:" in CTest memcheck:

Problem Statement

CTest memcheck by default hide memory test output to a MemoryTester log file. I need those errors to be printed on terminal.

Study the source code:

CTest memcheck by default add --log-file options to memory check.

Ways that I tried to display memory errors in terminal

1. Add --log-fd=2 to Valgrind option. This option can overwrite the default setting and print error messages in stderr. However, the source code has a function to print out "cannot find memory tester output file" message, in case the output is not redirected to the output file.
2. Use CTest --overwrite option. I tried to overwrite MEMORY_COMMAND_OPTIONS. However, that variable doesn't affect the default --log-file set up.
3. Use CTest -O option. However, this option only duplicate the terminal output to another file, instead of overwrite the --log-file flag.
4. Write a script to display memory errors in the end. This option will print all error messages in the end, and don't incur the tester file message. However, it's better to display memory error messages directly below failed test cases, so that users can keep track of which error messages is corresponding to which tests.