Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature_graphene_passive is floating #1055

Open
frolosofsky opened this issue May 3, 2019 · 1 comment
Open

feature_graphene_passive is floating #1055

frolosofsky opened this issue May 3, 2019 · 1 comment
Assignees
Labels
floating test A test that sometimes but not always fails
Milestone

Comments

@frolosofsky
Copy link
Member

It has flaked on the master branch recently.

2019-05-03T11:32:53.200000Z TestFramework (ERROR): Assertion failed
Traceback (most recent call last):
  File "/home/travis/build/dtr-org/unit-e/build/unit-e-x86_64-unknown-linux-gnu/test/functional/test_framework/test_framework.py", line 203, in main
    self.run_test()
  File "/home/travis/build/dtr-org/unit-e/build/unit-e-x86_64-unknown-linux-gnu/test/functional/feature_graphene_passive.py", line 70, in run_test
    self.test_non_synced_mempool(relay)
  File "/home/travis/build/dtr-org/unit-e/build/unit-e-x86_64-unknown-linux-gnu/test/functional/feature_graphene_passive.py", line 98, in test_non_synced_mempool
    graphene_tx = relay.wait_for((b'graphenetx', block_hash)).graphene_tx
  File "/home/travis/build/dtr-org/unit-e/build/unit-e-x86_64-unknown-linux-gnu/test/functional/feature_graphene_passive.py", line 291, in wait_for
    wait_until(lambda: get_msg() is not None, timeout=10)
  File "/home/travis/build/dtr-org/unit-e/build/unit-e-x86_64-unknown-linux-gnu/test/functional/test_framework/util.py", line 370, in wait_until
    raise AssertionError("Predicate {} not true after {} seconds".format(predicate_source, timeout))
AssertionError: Predicate (['        wait_until(lambda: get_msg() is not None, timeout=10)\n'], 291) not true after 10 seconds

Log is truncated unfortunately. log.txt

@frolosofsky frolosofsky added the floating test A test that sometimes but not always fails label May 3, 2019
@frolosofsky frolosofsky added this to the 0.2 milestone May 3, 2019
@frolosofsky frolosofsky changed the title graphene_passive is floating feature_graphene_passive is floating May 3, 2019
@castarco
Copy link

castarco commented May 21, 2019

I reproduced this error locally, it seems there's a problem at the time of re-conciliating the ILBTs (the same message does not appear when the tests pass).

node1 2019-05-21T13:26:17.903097Z [         net] received: graphenblock (733 bytes) peer=0 
 node1 2019-05-21T13:26:17.903121Z [         net] Received graphene block 2760ed72576efc311a25a0f943baade63accd457687aec5f9d60899fe0d69c9a from peer 0 
 node1 2019-05-21T13:26:17.903170Z [       bench] 'Graphene tx pool enumeration' took 0.04ms 
 node1 2019-05-21T13:26:17.903180Z [         net] Can not reconcile graphene block 2760ed72576efc311a25a0f943baade63accd457687aec5f9d60899fe0d69c9a. Receiver iblt has 65 txs, sender has 61 
 node1 2019-05-21T13:26:17.903188Z [       bench] 'GrapheneBlockReconstructor' took 0.06ms 
 node1 2019-05-21T13:26:17.903193Z [         net] Unable to decode iblt in graphene block 2760ed72576efc311a25a0f943baade63accd457687aec5f9d60899fe0d69c9a 
 node1 2019-05-21T13:26:17.903199Z [         net] sending getdata (37 bytes) peer=0 
 node0 2019-05-21T13:26:17.903424Z [         net] received: getdata (37 bytes) peer=0

feature_graphene_passive.log

P.D.: Not sure if we should fix this test or redesign it, because having IBLT reconciliation problems is something to be expected time to time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
floating test A test that sometimes but not always fails
Projects
None yet
Development

No branches or pull requests

3 participants