Commit 053c2d7d authored by Sean McGivern's avatar Sean McGivern

Fix a flaky profiler spec

The check against `uniq` was meant to ensure we had multiple entries for
the same time, because the profiled code has several items that take
close to zero seconds.

However, as we're now checking against all running threads, this doesn't
really make sense: not all running threads will have that property. And
even if they did, this wasn't a great spec anyway, because it's an
unlikely failure condition.
parent 02cc59de
......@@ -229,7 +229,6 @@ RSpec.describe Gitlab::Profiler do
.map { |(total)| total.to_f }
expect(total_times).to eq(total_times.sort.reverse)
expect(total_times).not_to eq(total_times.uniq)
end
end
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment