[Test Framework] Support setting the p2p/RPC port range over the cmd line #8022

issue fanquake opened this issue on May 8, 2016
  1. fanquake commented at 4:11 AM on May 8, 2016: member

    "For supporting multiple tests running in parallel, I think it might make sense to add support to the test framework for specifying a range of ports to use for the p2p and rpc ports on the command line, which the rpc_tests.py script could use. The logic now of hoping that pid's don't collide modulo some big number is not sufficiently robust in my opinion."

    Original comment from @sdaftuar here.

  2. MarcoFalke added the label Tests on May 8, 2016
  3. MarcoFalke added the label Priority Low on May 9, 2016
  4. MarcoFalke commented at 7:40 PM on May 9, 2016: member

    #7972 includes a patch (ccccc59) to pass in a seed instead of relying on os.getpid(). Not sure if more than that is required/wanted.

  5. MarcoFalke closed this on May 22, 2016

  6. DrahtBot locked this on Sep 8, 2021

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-17 09:15 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me