starred/json
1
0
Fork 0
mirror of https://github.com/nlohmann/json.git synced 2026-09-27 06:10:44 +01:00
Code Issues Packages Projects Releases 10 Wiki Activity

Diff fewer nesting depths so the test does not time out under Valgrind

Browse Source 
Checking every depth up to 300 made test-json_patch exceed the 1500 s ctest
timeout in ci_test_valgrind. Check the depths up to 16, those around the
recursion limit of 128, and 300 instead.

Signed-off-by: Niels Lohmann <mail@nlohmann.me>
This commit is contained in:
Niels Lohmann
2026-09-25 08:21:38 +02:00
parent 08e30eca78
commit 484f644b86
1 changed files with 16 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/src/unit-json_patch.cpp
+16 -3
View File
@@ -16,6 +16,7 @@ using nlohmann::json;
#include <fstream>
#include <string>
#include <vector>
#include "make_test_data_available.hpp"
namespace
@@ -1812,9 +1813,21 @@ TEST_CASE("JSON patch: diff of deeply nested values")
{
SECTION("the diff reproduces the target at every depth")
{
// every depth on either side of the nesting depth up to which diff()
// recurses (detail::recursion_depth_limit(), 128)
for (std::size_t depth = 0; depth <= 300; ++depth)
// depths on either side of the nesting depth up to which diff()
// recurses (detail::recursion_depth_limit(), 128); not every depth up
// to 300, as the test would then time out under Valgrind
std::vector<std::size_t> depths;
for (std::size_t depth = 0; depth <= 16; ++depth)
{
depths.push_back(depth);
}
for (std::size_t depth = 120; depth <= 136; ++depth)
{
depths.push_back(depth);
}
depths.push_back(300);
for (const auto depth : depths)
{
CAPTURE(depth);
for (int from = 0; from < 3; ++from)