From 264b2d1975e88b0327bb8c5c4ec9016402dd1d8f Mon Sep 17 00:00:00 2001
From: Christian Decker <decker.christian@gmail.com>
Date: Mon, 13 Apr 2020 15:31:22 +0200
Subject: [PATCH] pyln-testing: Add more meaningful error for mock_estimatefees

We only support a very limited number of argument combinations, and apparently
sometimes we trigger a case we aren't handling. This adds a more useful error
message, including the params we didn't match.
---
 contrib/pyln-testing/pyln/testing/utils.py | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/contrib/pyln-testing/pyln/testing/utils.py b/contrib/pyln-testing/pyln/testing/utils.py
index bb7ca15e2..92bde08c0 100644
--- a/contrib/pyln-testing/pyln/testing/utils.py
+++ b/contrib/pyln-testing/pyln/testing/utils.py
@@ -871,7 +871,9 @@ class LightningNode(object):
             elif params == [100, 'ECONOMICAL']:
                 feerate = feerates[3] * 4
             else:
-                raise ValueError()
+                raise ValueError("Don't have a feerate set for {}/{}.".format(
+                    params[0], params[1],
+                ))
             return {
                 'id': r['id'],
                 'error': None,