Merge #20955: test: Fix get_previous_releases.py for aarch64

2021/1/19 アクティビティ

Merge #20955: test: Fix get_previous_releases.py for aarch64

fa1d5e51374bce9607b429836bbd3fe059e3c78c test: Fix get_previous_releases.py for aarch64 (MarcoFalke)

Pull request description:

  Otherwise it will fail with "Not sure which binary to download..."

ACKs for top commit:
  laanwj:
    Code review ACK fa1d5e51374bce9607b429836bbd3fe059e3c78c

Tree-SHA512: 0db71e898a431665757ce835016a4e05c629a95abc4a2951eac9bd9b5876ec3dc3d6f156d58565e2bcdf918cde4f2649183d4a58038ac13c705a7e914c0094d1

情報元 - Merge #20955: test: Fix get_previous_releases.py for aarch64 · bitcoin/[email protected] · GitHub

Merge #20955: test: Fix get_previous_releases.py for aarch64 · bitcoin/bitcoin@991e612 · GitHub

フォローする

bitcoin, BTC, Fix get_previous_releases, Merge, py for aarch64, test 1of.biz

depends: clang 6.0.1

depends: clang 6.0.1 This also removes some now-unnecessary cctools hacks. Co-Authored-By: Cory Fields <[email protected]>

記事を読む

Merge #15305: [validation] Crash if disconnecting a block fails

<pre>Merge #15305: [validation] Crash if disconnecting a block fails a47df13471e3168e2e02023fb20cdf2414141b36 [qa] Test disconnect block failure -> shutdown (Suhas Daftuar) 4433ed0f730cfd60eeba3694ff3c283ce2c0c8ee [validation] Crash if disconnecting a block fails (Suhas Daftuar) Pull request description: If we're unable to disconnect a block during normal operation, then that is a failure of our local system (such as disk failure) or the chain that we are on (eg CVE-2018-17144), but cannot be due to failure of the (more work) chain that we're trying to validate. We should abort rather than stay on a less work chain. Fixes #14341. ACKs for top commit: practicalswift: utACK a47df13471e3168e2e02023fb20cdf2414141b36 TheBlueMatt: utACK a47df13471e3168e2e02023fb20cdf2414141b36. Didn't bother to review the test in detail, it looked fine. Debated whether invalidateblock should ever crash the node, but *not* crashing in the case of hitting a pruned block (which is the only change here) is clearly better, even if there are other cases I'd argue we should crash in. ryanofsky: utACK a47df13471e3168e2e02023fb20cdf2414141b36. Only change since last review is new comment. promag: ACK a47df1347, it takes awhile to quit (RPC connection timeouts) but that's unrelated - hope to fix that soon. fanquake: ACK a47df13471e3168e2e02023fb20cdf2414141b36 Tree-SHA512: 4dec8cef6e7dbbe513c138fc5821a7ceab855e603ece3c16185b51a3830ab7ebbc844a28827bf64e75326f45325991dcb672f13bd7baede53304f27289c4af8d</pre>

記事を読む

test: Bump timeouts in slow running tests

記事を読む

GUI: Allow generating Bech32 addresses with a legacy-address default

記事を読む

fuzz: Consolidate fuzzing TestingSetup initialization

<pre>fuzz: Consolidate fuzzing TestingSetup initialization Previously, the {Basic,}TestingSetup for fuzzers were set up in many ways: 1. Calling InitializeFuzzingContext, which implicitly constructs a static const BasicTestingSetup 2. Directly constructing a static const BasicTestingSetup in the initialize_* function 3. Directly constructing a static TestingSetup and reproducing the initialization arguments (I'm assuming because InitializeFuzzingContext only initializes a BasicTestingSetup) The new, relatively-simple MakeFuzzingContext function allows us to consolidate these methods of initialization by being flexible enough to be used in all situations. It: 1. Is templated so that we can choose to initialize any of the *TestingSetup classes 2. Has sane defaults which are often used in fuzzers but are also easily overridable 3. Returns a unique_ptr, explicitly transferring ownership to the caller to deal with according to its situation</pre>

記事を読む

First Hyperledger-based cryptocurrency explodes 486% overnight on Bittrex BTC listing

Merge #20884: script: Improve robustness of bitcoind.service on startup