Skip to content

Fix/test framework hang#251

Merged
JacobBorden merged 19 commits intodevelopmentfrom
fix/test-framework-hang
Jul 4, 2025
Merged

Fix/test framework hang#251
JacobBorden merged 19 commits intodevelopmentfrom
fix/test-framework-hang

Conversation

@JacobBorden
Copy link
Owner

No description provided.

JacobBorden and others added 19 commits July 2, 2025 17:46
This commit includes the following changes and progress:

1.  **Build System Setup & Dependency Installation:**
    *   Successfully configured the CMake build environment.
    *   Installed missing system dependencies: `libfuse3-dev`, `libboost-dev`, `libboost-system-dev`, `libgrpc++-dev`, `protobuf-compiler-grpc`.

2.  **Libsodium Build Fix:**
    *   Modified the root `CMakeLists.txt` to correctly build the `libsodium` library, which is fetched using `FetchContent`. This involved adding `execute_process` calls to run `configure`, `make`, and `make install` for libsodium.
    *   Corrected the `make` command for libsodium to properly use the number of available processors (`nproc`).
    *   Updated `tests/CMakeLists.txt` to ensure that FUSE test executables correctly include `SODIUM_INCLUDE_DIRS`.

3.  **Project Build:**
    *   The project now builds successfully after the above fixes.

4.  **Test Execution Issue (Unresolved):**
    *   Encountered a persistent issue where running any Google Test executable (either via CTest or directly) results in a timeout.
    *   This hang occurs even with a minimal GTest setup (`MinimalTest`) that includes only GTest itself and no project-specific code.
    *   Troubleshooting steps taken:
        *   Simplified `tests/tests_main.cpp` by commenting out custom initializations (Logger, KeyManager).
        *   Downgraded Google Test from v1.14.0 to release-1.10.0.
        *   Ensured the minimal test was correctly added to CMake and CTest.
    *   The root cause of the GTest hang could not be determined within the available time and tools, suggesting a deeper incompatibility with the testing environment or toolchain.

Due to the inability to run tests and gather feedback, further debugging of application-specific logic based on test failures was not possible. The primary focus shifted to resolving build issues and attempting to get the test framework operational.
…e-for-tests

Fix var_dir path configuration
…th-node-name

Fix node file collisions in tests
…1.47-and-reintroduce-features

Restore AGENTS test guidelines
…es-for-metaserver-and-nodes

feat: periodic state saves
…ion-failure

Fix decryption crash in file verifier
…glethreadtest-failure

Fix fuse concurrency wrapper
…n-fuse-tests

Fix SIMPLIDFS_CLUSTER_KEY handling in FUSE wrapper
@JacobBorden JacobBorden merged commit 02aaa40 into development Jul 4, 2025
3 of 4 checks passed
@JacobBorden JacobBorden deleted the fix/test-framework-hang branch July 4, 2025 13:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant