Fix test expectations for compiler peak memory
TBR=machenbach@chromium.org Bug: chromium:901329 Change-Id: Id9bc01e7e49c90ac3b5bca88abba53a38a1b0d80 Reviewed-on: https://chromium-review.googlesource.com/c/1326021 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#57348}
This commit is contained in:
parent
80dd5e62dc
commit
ec55cc0f6f
@ -906,9 +906,9 @@ TEST(DeepEagerCompilationPeakMemory) {
|
||||
CHECK_LE(peak_mem_1, peak_mem_2);
|
||||
CHECK_EQ(peak_mem_2, peak_mem_3);
|
||||
CHECK_LE(peak_mem_3, peak_mem_4);
|
||||
// Check that eager compilation does not cause significantly higher (+25%)
|
||||
// Check that eager compilation does not cause significantly higher (+100%)
|
||||
// peak memory than lazy compilation.
|
||||
CHECK_LE(peak_mem_4 - peak_mem_3, peak_mem_3 / 4);
|
||||
CHECK_LE(peak_mem_4 - peak_mem_3, peak_mem_3);
|
||||
}
|
||||
|
||||
} // namespace internal
|
||||
|
Loading…
Reference in New Issue
Block a user