mirror of
https://github.com/ElementsProject/lightning.git
synced 2025-02-22 14:42:40 +01:00
pytest: fix flake in test_channel_persistence w/ TEST_CHECK_DBSTMTS
This was weird. Here is the message (with \n turned into real new lines): ``` 2022-07-24T07:20:08.9144998Z Plugin '/home/runner/work/lightning/lightning/tests/plugins/dblog.py' returned an invalid response to the db_write hook: {"jsonrpc": "2.0", "id": 40, "error": {"code": -32600, "message": "Error while processing db_write: UNIQUE constraint failed: shachain_known.shachain_id, shachain_known.pos", "traceback": "Traceback (most recent call last): File \"/home/runner/work/lightning/lightning/contrib/pyln-client/pyln/client/plugin.py\", line 631, in _dispatch_request result = self._exec_func(method.func, request) File \"/home/runner/work/lightning/lightning/contrib/pyln-client/pyln/client/plugin.py\", line 616, in _exec_func return func(*ba.args, **ba.kwargs) File \"/home/runner/work/lightning/lightning/tests/plugins/dblog.py\", line 45, in db_write plugin.conn.execute(c) sqlite3.IntegrityError: UNIQUE constraint failed: shachain_known.shachain_id, shachain_known.pos "}} ``` Finally, I realized that we *kill* l2: this means it has updated the plugin db but not the real db. This is expected: a real backup plugin would handle this case. Simply disable the test for this case. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
This commit is contained in:
parent
008a59b004
commit
8da361b49b
1 changed files with 2 additions and 0 deletions
|
@ -2203,6 +2203,8 @@ def test_funding_while_offline(node_factory, bitcoind):
|
|||
@pytest.mark.developer
|
||||
@pytest.mark.openchannel('v1')
|
||||
@pytest.mark.openchannel('v2')
|
||||
@unittest.skipIf(os.environ.get("TEST_CHECK_DBSTMTS", None) == "1",
|
||||
"We kill l2, dblog plugin replay will be unreliable")
|
||||
def test_channel_persistence(node_factory, bitcoind, executor):
|
||||
# Start two nodes and open a channel (to remember). l2 will
|
||||
# mysteriously die while committing the first HTLC so we can
|
||||
|
|
Loading…
Add table
Reference in a new issue