Skip to content

ariadne_runtime_test: a predicate cut by the time cap passes however it is reported #680

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
transfix merged 1 commit into from
Oct 18, 2026
Merged

ariadne_runtime_test: a predicate cut by the time cap passes however it is reported #680

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion src/cvc/tests/ariadne_runtime_test.cpp
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1679,7 +1679,12 @@ TEST(AriadneStdlib, PredicateMaterializerIsCutByTheEvalBudget) {
EXPECT_FALSE(mb.saw("text_line:big"));
auto warns = rt.take_reactive_warnings();
ASSERT_FALSE(warns.empty());
EXPECT_NE(warns[0].find("exceeded the eval budget"), std::string::npos) << warns[0];
// Cut by the step cap or the time cap, whichever comes first. The time cap is reported as the
// eval budget when it expires between steps, and through the job's own error ("evaluation
// exceeded time budget") when the job's deadline poll sees it first, as on a slow Debug build.
EXPECT_TRUE(warns[0].find("exceeded the eval budget") != std::string::npos ||
warns[0].find("evaluation exceeded time budget") != std::string::npos)
<< warns[0];

// A 0 here still slices, at the host's 1024 nodes a step, and an ordinary call finishes. It is
// kept small so it fits the 5 ms time cap in a Debug build on a loaded CI runner.
Expand Down
Loading