Fix profiler_submission benchmark to work with new Flush object

The benchmark was broken by the addition of a `code_provenance` field to the flush object, which is not relevant to this benchmark. I did a bit of magic in a REPL to update the marshalled data to not break the benchmark.
DataDog · Dec 16, 2021 · fbf98bd · fbf98bd
1 parent 1a18d71
commit fbf98bd
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 0 deletions.
diff --git a/benchmarks/data/profiler-submission-marshal.gz b/benchmarks/data/profiler-submission-marshal.gz
diff --git a/benchmarks/profiler_submission.rb b/benchmarks/profiler_submission.rb
@@ -8,6 +8,7 @@
 require 'benchmark/ips'
 require 'ddtrace'
 require 'pry'
+require 'digest'
 require_relative 'dogstatsd_reporter'
 
 # This benchmark measures the performance of encoding pprofs and trying to submit them