plugin: Increase manifest timeout to 60 seconds

Valgrind seems to be slowing the pay-plugin down enough for the 10 seconds timeout to get triggered on a semi-regular basis. Reported-by: Rusty Russell <@rustyrussell> Signed-off-by: Christian Decker <[email protected]>
flo071 · Jan 20, 2019 · c78d7e0 · c78d7e0
1 parent 82ff580
commit c78d7e0
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/contrib/plugins/fail/failtimeout.py b/contrib/plugins/fail/failtimeout.py
@@ -9,8 +9,8 @@
 
 
 def json_getmanifest(request):
-    # Timeout is 10 seconds, so wait 11
-    time.sleep(11)
+    # Timeout is 60 seconds, so wait 11
+    time.sleep(61)
     return {
         "options": [
         ],

diff --git a/lightningd/plugin.c b/lightningd/plugin.c
@@ -31,7 +31,7 @@
  * hangs we can't do much, so we put an upper bound on the time we're
  * willing to wait. Plugins shouldn't do any initialization in the
  * `getmanifest` call anyway, that's what `init `is for. */
-#define PLUGIN_MANIFEST_TIMEOUT 10
+#define PLUGIN_MANIFEST_TIMEOUT 60
 
 struct plugin {
 	struct list_node list;