These benchmarks measured no execution time, so their results are not comparable and count as unchanged. This usually happens when the compiler removes the code under test.
The flamegraph wasn't generated: most of the time was spent in runtime internals, which would leave nothing useful to analyze. (1 benchmark)
The flamegraph wasn't generated: no execution data was recorded while the benchmark ran. Make sure the compiler didn't optimize the benchmark out. (32 benchmarks)