pytest: wait for stderr, rather than asserting.
Two almost identical assertion fails under CI. Try waiting. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
This commit is contained in:
parent
2f27aad8d0
commit
c1a111b68c
@ -244,7 +244,7 @@ def test_only_announce_one_dns(node_factory, bitcoind):
|
||||
# and test that we can't announce more than one DNS address
|
||||
l1 = node_factory.get_node(may_fail=True, expect_fail=True,
|
||||
options={'announce-addr': ['localhost.localdomain:12345', 'example.com:12345']})
|
||||
assert l1.daemon.is_in_stderr("Only one DNS can be announced")
|
||||
wait_for(lambda: l1.daemon.is_in_stderr("Only one DNS can be announced"))
|
||||
|
||||
|
||||
@pytest.mark.developer("needs DEVELOPER=1")
|
||||
|
||||
@ -95,7 +95,7 @@ def test_option_types(node_factory):
|
||||
|
||||
# the node should fail to start, and we get a stderr msg
|
||||
assert not n.daemon.running
|
||||
assert n.daemon.is_in_stderr('bool_opt: ! does not parse as type bool')
|
||||
wait_for(lambda: n.daemon.is_in_stderr('bool_opt: ! does not parse as type bool'))
|
||||
|
||||
# What happens if we give it a bad int-option?
|
||||
n = node_factory.get_node(options={
|
||||
|
||||
Loading…
Reference in New Issue
Block a user