From 94c90b0127de32a66eeee0417432d9731cd09039 Mon Sep 17 00:00:00 2001
From: Paul Lee <paullee23@meta.com>
Date: Fri, 12 Jul 2024 09:44:10 -0700
Subject: [PATCH] Re-enable TestFrame.UpdateMemory

Summary: Issue causing GCC build to exhibit different behavior and cause `TestFrame.UpdateMemory()` to fail has been addressed.  Re-enable test in Github workflow.

Reviewed By: enpe

Differential Revision: D59473025

fbshipit-source-id: b7ec373305a8a80b05fc89c4f931e644c81e4274
---
 .github/workflows/build_linux.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/build_linux.yml b/.github/workflows/build_linux.yml
index ced2855cf..2cf738a82 100644
--- a/.github/workflows/build_linux.yml
+++ b/.github/workflows/build_linux.yml
@@ -107,7 +107,7 @@ jobs:
           install-path: ${{ env.OCEAN_INSTALL_PATH }}/linux_static_${{ matrix.build_config }}
           test-directory: impl/ocean/test/testbase
           # Exclude tests that are known to fail
-          ctest-args: '-E TestHighPerformanceTimer|TestSignal|TestFrame.UpdateMemory'
+          ctest-args: '-E TestHighPerformanceTimer|TestSignal'
 
   testcv-AdvancedFrame:
     name: Run ctest in testcv (TestAdvancedFrame) (${{ matrix.build_config }}, static)