Open Rqnsom opened 1 week ago
I note that xz and bzip2 both seem to get >3000x compression on a sample .trace file. I wonder if we can use compress_io
to automatically compress and decompress the .trace file. I note that the trace file is created in third_party/move/move-vm/runtime/src/tracing.rs
, the filename to write is set in third_party/move/tools/move-cli/src/base/test.rs
(var trace_path
, which is used to set env var MOVE_VM_TRACE
), coverage map is computed from that trace file, specified also in tests.rs
, but read in function CoverageMap::update_coverage_from_trace_file()
, defined in third_party/move/tools/move-coverage/src/coverge_map.rs
. Perhaps another library would be superior.
π Bug
While performing many tests with the
move-mutation-tool
, I noticed the.trace
file can grow a lot, from 800Mb to 56Gb. This caused me to run out of space a couple of times since our tool copies the package under test to a randomly generated folder in the/tmp/
directory. Not sure if this is normal, but it does seem strange.To reproduce
I am not completely sure how to reproduce this yet, but I noticed this a few times (after my OS reported "low disk space" warnings).
Expected Behavior
The expected size should be much lower. For example, the other coverage file,
.coverage_map.mvcov
, has only 901Kb.System information
Additional context
I will post new info if I manage to reproduce it again - but I created a workaround in our tool to delete the
.trace
file: #56 feat: optimization - delete .trace file