Set the default memprof serialization format as binary. For the tests,
we update the configuration to include 'print_text=true'.
Details
- Reviewers
tejohnson - Commits
- rGaacaebc6c22f: [memprof] Make the raw binary format the default.
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Half of the tests (9/18) fail if the default is set to the binary format.
Failed Tests (9):
MemProfiler-x86_64-linux :: TestCases/dump_process_map.cpp MemProfiler-x86_64-linux :: TestCases/log_path_test.cpp MemProfiler-x86_64-linux :: TestCases/memprof_merge_mib.cpp MemProfiler-x86_64-linux :: TestCases/memprof_profile_dump.cpp MemProfiler-x86_64-linux :: TestCases/test_malloc_load_store.c MemProfiler-x86_64-linux :: TestCases/test_memintrin.cpp MemProfiler-x86_64-linux :: TestCases/test_new_load_store.cpp MemProfiler-x86_64-linux :: TestCases/test_terse.cpp MemProfiler-x86_64-linux :: TestCases/unaligned_loads_and_stores.cpp
IMO it's probably better to be explicit in the test - e.g. we are already setting log_path=stderr for all of these I believe.
compiler-rt/test/memprof/lit.cfg.py | ||
---|---|---|
37 | I noticed that the other sanitizers (e.g. llvm/llvm-project/compiler-rt/test/asan/lit.cfg.py) add the trailing ":" after setting e.g. ASAN_OPTIONS. Will we end up with an extra trailing ":" for that env var? |
compiler-rt/test/memprof/lit.cfg.py | ||
---|---|---|
37 | Yes, thats a little bit cleaner though we could still end up with a trailing ':' if the test does not provide any options. Since these do not affect option parsing, I'm happy to update this to be consistent with the ASAN config. |
I can't reproduce the patch application failure on the buildbot. I applied the patches in series to a clean llvm repo and it worked.
I noticed that the other sanitizers (e.g. llvm/llvm-project/compiler-rt/test/asan/lit.cfg.py) add the trailing ":" after setting e.g. ASAN_OPTIONS. Will we end up with an extra trailing ":" for that env var?