test: try to reproduce #4215

dragonflydb · Dec 3, 2024 · 86ba6e8 · 86ba6e8
1 parent b0d633f
commit 86ba6e8
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 6 deletions.
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
@@ -132,9 +132,9 @@ jobs:
       - name: C++ Unit Tests
         run: |
           cd ${GITHUB_WORKSPACE}/build
-          echo Run ctest -V -L DFLY
+          echo Run ctest -R rdb_test -V --repeat-until-fail 1000
           GLOG_alsologtostderr=1 GLOG_vmodule=rdb_load=1,rdb_save=1,snapshot=1 \
-          FLAGS_list_experimental_v2=true timeout 20m ctest -V -L DFLY
+          FLAGS_list_experimental_v2=true timeout 60m ctest -R rdb_test -V --repeat-until-fail 100
 
           echo "Running tests with --force_epoll"
 
@@ -147,15 +147,15 @@ jobs:
           EOF
 
           gdb -ix ./init.gdb --batch -ex r --args ./dragonfly_test --force_epoll
-          FLAGS_force_epoll=true GLOG_vmodule=rdb_load=1,rdb_save=1,snapshot=1 timeout 20m ctest -V -L DFLY
+          FLAGS_force_epoll=true GLOG_vmodule=rdb_load=1,rdb_save=1,snapshot=1 timeout 60m ctest -R rdb_test -V --repeat-until-fail 100
 
           echo "Finished running tests with --force_epoll"
 
           echo "Running tests with --cluster_mode=emulated"
-          FLAGS_cluster_mode=emulated timeout 20m ctest -V -L DFLY
+          FLAGS_cluster_mode=emulated timeout 60m ctest -R rdb_test -V --repeat-until-fail 100
 
           echo "Running tests with both --cluster_mode=emulated & --lock_on_hashtags"
-          FLAGS_cluster_mode=emulated FLAGS_lock_on_hashtags=true timeout 20m ctest -V -L DFLY
+          FLAGS_cluster_mode=emulated FLAGS_lock_on_hashtags=true timeout 60m ctest -R rdb_test -V --repeat-until-fail 100
 
           timeout 5m ./dragonfly_test
           timeout 5m ./multi_test --multi_exec_mode=1

diff --git a/src/server/db_slice.cc b/src/server/db_slice.cc
@@ -588,7 +588,9 @@ OpResult<DbSlice::AddOrFindResult> DbSlice::AddOrFindInternal(const Context& cnt
   // If we are over limit in non-cache scenario, just be conservative and throw.
   if (apply_memory_limit && !caching_mode_ && memory_budget_ + memory_offset < 0) {
     LOG_EVERY_T(WARNING, 1) << "AddOrFind: over limit, budget: " << memory_budget_
-                            << " reclaimed: " << reclaimed << " offset: " << memory_offset;
+                            << " reclaimed: " << reclaimed << " offset: " << memory_offset
+                            << "max_memory_limit" << max_memory_limit << "used_mem_current"
+                            << used_mem_current;
     events_.insertion_rejections++;
     return OpStatus::OUT_OF_MEMORY;
   }