azalea/kotlin-fork
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[K/N] Adjust timings in GCSchedulerTest

Browse Source 
Merge-request: KT-MR-5555
Merged-by: Alexander Shabalin <Alexander.Shabalin@jetbrains.com>
This commit is contained in:
Alexander Shabalin
2022-01-25 09:38:32 +00:00
committed by Space
parent 2e5a110a3e
commit b29b6227c2
1 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
kotlin-native/runtime/src/gc/common/cpp/GCSchedulerTest.cpp
+8 -8
View File
@@ -580,17 +580,17 @@ TEST(GCSchedulerDataWithTimer, CollectOnTimeoutReached) {
constexpr int mutatorsCount = kDefaultThreadCount;
GCSchedulerConfig config;
config.regularGcIntervalMicroseconds = std::chrono::microseconds(std::chrono::milliseconds(200)).count();
config.regularGcIntervalMicroseconds = std::chrono::microseconds(std::chrono::milliseconds(2000)).count();
config.autoTune = false;
config.targetHeapBytes = std::numeric_limits<size_t>::max();
GCSchedulerDataTestApi<compiler::GCSchedulerType::kWithTimer, mutatorsCount> schedulerTestApi(config);
EXPECT_CALL(schedulerTestApi.scheduleGC(), Call()).Times(0);
schedulerTestApi.advance_time(std::chrono::milliseconds(100));
schedulerTestApi.advance_time(std::chrono::milliseconds(1000));
testing::Mock::VerifyAndClearExpectations(&schedulerTestApi.scheduleGC());
EXPECT_CALL(schedulerTestApi.scheduleGC(), Call());
schedulerTestApi.advance_time(std::chrono::milliseconds(150));
schedulerTestApi.advance_time(std::chrono::milliseconds(1500));
testing::Mock::VerifyAndClearExpectations(&schedulerTestApi.scheduleGC());
schedulerTestApi.OnPerformFullGC();
schedulerTestApi.UpdateAliveSetBytes(0);
@@ -600,13 +600,13 @@ TEST(GCSchedulerDataWithTimer, FullTimeoutAfterLastGC) {
constexpr int mutatorsCount = kDefaultThreadCount;
GCSchedulerConfig config;
config.regularGcIntervalMicroseconds = std::chrono::microseconds(std::chrono::milliseconds(200)).count();
config.regularGcIntervalMicroseconds = std::chrono::microseconds(std::chrono::milliseconds(2000)).count();
config.autoTune = false;
config.targetHeapBytes = 10;
GCSchedulerDataTestApi<compiler::GCSchedulerType::kWithTimer, mutatorsCount> schedulerTestApi(config);
EXPECT_CALL(schedulerTestApi.scheduleGC(), Call()).Times(0);
schedulerTestApi.advance_time(std::chrono::milliseconds(100));
schedulerTestApi.advance_time(std::chrono::milliseconds(1000));
testing::Mock::VerifyAndClearExpectations(&schedulerTestApi.scheduleGC());
EXPECT_CALL(schedulerTestApi.scheduleGC(), Call());
@@ -616,18 +616,18 @@ TEST(GCSchedulerDataWithTimer, FullTimeoutAfterLastGC) {
schedulerTestApi.UpdateAliveSetBytes(0);
EXPECT_CALL(schedulerTestApi.scheduleGC(), Call()).Times(0);
schedulerTestApi.advance_time(std::chrono::milliseconds(150));
schedulerTestApi.advance_time(std::chrono::milliseconds(1500));
// It's now 250 ms since the start, but only 150ms since previous collection.
// However, the timer has fired once ~50ms ago.
testing::Mock::VerifyAndClearExpectations(&schedulerTestApi.scheduleGC());
EXPECT_CALL(schedulerTestApi.scheduleGC(), Call()).Times(0);
schedulerTestApi.advance_time(std::chrono::milliseconds(100));
schedulerTestApi.advance_time(std::chrono::milliseconds(1000));
// It's now 250 ms since the previous collection, but the timer will fire in ~50ms.
testing::Mock::VerifyAndClearExpectations(&schedulerTestApi.scheduleGC());
EXPECT_CALL(schedulerTestApi.scheduleGC(), Call());
schedulerTestApi.advance_time(std::chrono::milliseconds(100));
schedulerTestApi.advance_time(std::chrono::milliseconds(1000));
// 350ms since previous collection, and the timer has fired ~50ms ago.
testing::Mock::VerifyAndClearExpectations(&schedulerTestApi.scheduleGC());
schedulerTestApi.OnPerformFullGC();