From e3a6c9086afe2693e56d3c941043405455b6d7ac Mon Sep 17 00:00:00 2001 From: Ian Roddis Date: Fri, 28 Jan 2022 14:36:33 -0400 Subject: [PATCH] Removing verbose logging --- daggyr/libdaggyr/src/Server.cpp | 3 --- libdaggy/src/DAGRunner.cpp | 2 +- 2 files changed, 1 insertion(+), 4 deletions(-) diff --git a/daggyr/libdaggyr/src/Server.cpp b/daggyr/libdaggyr/src/Server.cpp index 9364c4b..869d2cb 100644 --- a/daggyr/libdaggyr/src/Server.cpp +++ b/daggyr/libdaggyr/src/Server.cpp @@ -142,9 +142,6 @@ namespace daggy::daggyr { auto runID = request.param(":runID").as(); auto taskName = request.param(":taskName").as(); - std::cout << "Received request for " << runID << " / " << taskName - << std::endl; - Capacity resourcesUsed; Task task; try { diff --git a/libdaggy/src/DAGRunner.cpp b/libdaggy/src/DAGRunner.cpp index c2773a3..1c39f0a 100644 --- a/libdaggy/src/DAGRunner.cpp +++ b/libdaggy/src/DAGRunner.cpp @@ -101,7 +101,7 @@ namespace daggy { /* In cases where there are many tasks ready to execute, the blocking nature of executor_.execute(...) means - that tasks will get executed and the futures resolve, + that tasks will get executed and the futures resolved, but we won't know until all pending tasks are enqueued. To avoid this, submit at most MAX_SUBMITS tasks before