Skip to content

Conversation

sdaftuar
Copy link
Member

I noticed intermittent failures in the mempool_packages.py RPC test; turns out I introduced a race condition in a recent pull (#7062).

Before this change, node1 could either be in sync or out of sync with node0 after invalidateblock was called, depending on how fast that happened. The test would fail if they were out of sync. This fixes the test by enforcing that their tips stay synced up.

@laanwj Note that this bug is in 0.12, in case you think this should be backported or included in the next 0.12 release candidate.

@maflcko
Copy link
Member

maflcko commented Jan 18, 2016

ACK 4d10d2e.

Also needs to be tagged with [Backport]

@laanwj laanwj merged commit 4d10d2e into bitcoin:master Jan 18, 2016
laanwj added a commit that referenced this pull request Jan 18, 2016
4d10d2e Eliminate race condition in mempool_packages test (Suhas Daftuar)
laanwj pushed a commit that referenced this pull request Jan 18, 2016
random-zebra added a commit to PIVX-Project/PIVX that referenced this pull request Apr 7, 2021
600dd4d Eliminate race condition in mempool_packages test (Suhas Daftuar)

Pull request description:

  Solving the intermittent failures in mempool_packages test that happen way too often.
  Coming straight from bitcoin#7368.

  PD: thanks to my good zebra for finding the cause

ACKs for top commit:
  random-zebra:
    utACK 600dd4d

Tree-SHA512: 4fc5fdf3ced4f359268c0e761a7a16943ab1a88c4fa5573b50e89163bebe7d01b1b22d5b25fee3cc80a534acd36e1b92e3519646b02dd34f8645d3123b6ecbb1
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants