It looks like it needs rebase again. I guess we can push it back to rc3 (if there is one) or 0.20.1
laanwj
commented at 3:02 pm on May 14, 2020:
member
I must say the problem that #18902 solves is unclear to me. Does it affect the gitian build as we use to build the release, in practice? If so what is the user-visible issue? If not, If it’s some more theoretical or aesthetic I’d strongly prefer pushing it back to 0.20.1 (especially as it makes large changes to the gitian descriptor).
MarcoFalke
commented at 3:08 pm on May 14, 2020:
member
Ok, updated OP to remove #18287 and #18818 for now.
MarcoFalke
commented at 4:30 pm on May 14, 2020:
member
test: Add unregister_validation_interface_race test
This commit is (intentionally) adding a broken test. The test is broken
because it registering a subscriber object that can go out of scope
while events are still being sent.
To run the broken test and reproduce the bug:
- Remove comment /** and */
- ./configure --with-sanitizers=address
- export ASAN_OPTIONS=detect_leaks=0
- make
- while ./src/test/test_bitcoin -t validationinterface_tests/unregister_validation_interface_race --catch_system_errors=no ; do true; done
Github-Pull: #18742
Rebased-From: fab6d060ce5f580db538070beec1c5518c8c777c
37a620748b
miner: Avoid stack-use-after-return in validationinterface
This is achieved by switching to a shared_ptr.
Also, switch the validationinterfaces in the tests to use shared_ptrs
for the same reason.
Github-Pull: #18742
Rebased-From: 7777f2a4bb1f9d843bc50a4e35085cfbb2808780
cc7d34465b
test: Remove const to work around compiler error on xenial
Fix the following error in travis:
test/validationinterface_tests.cpp:26:36: error: default initialization of an object of const type 'const BlockValidationState' without a user-provided default constructor
const BlockValidationState state_dummy;
Github-Pull: #18975
Rebased-From: 050e2ee6f28e7b31c167013be7313726e34084e9
cf2a6e2a39
[net processing] Only send a getheaders for one block in an INV
Headers-first is the primary method of announcement on the network. If a
node fell back sending blocks by inv, it's probably for a re-org. The
final block hash provided should be the highest, so send a getheaders
and then fetch the blocks we need to catch up.
Github-Pull: #18962
Rebased-From: 746736639e6d05acdb85c866d4c605c947d4c500
6161c94a61
fanquake force-pushed
on May 15, 2020
fanquake
commented at 0:14 am on May 15, 2020:
member
fanquake
commented at 4:22 am on May 15, 2020:
member
If you feel strongly about the fuzzers being green, I can recommend #18757
I’ve now added this as well.
fanquake
commented at 6:15 am on May 15, 2020:
member
I’ve now added this as well.
script/script.h:332:35: runtime error: negation of -9223372036854775808 cannot be represented in type ‘int64_t’ (aka ’long’); cast to an unsigned type to negate this value to itself
#0 0x55f522f90e9e in CScriptNum::serialize(long const&) /home/travis/build/bitcoin/bitcoin/build/bitcoin-x86_64-pc-linux-gnu/src/./script/script.h:332:35
Looks like the fuzzers are not going to pass without even more backports (maybe #18413, possibly others), which I don’t want to do at this point. I’d be happy to remove the fuzz job on this branch, and just have them running on master. If anyone agrees I’ll drop 9a8fb4cf4ba472a5c3e1b9b71d31673f881a4896 off here.
laanwj
commented at 7:23 am on May 15, 2020:
member
ACK on simply disabling fuzzers that don’t pass for now when they fail for a known reason (and perhaps fix them in later 0.20.x).
test: disable script fuzz tests
Given that #18413 has not been backported.
245c862cfd
fanquake force-pushed
on May 15, 2020
promag
commented at 9:20 am on May 15, 2020:
member
Tested ACK245c862cfd4883ea91b53d766abb00a9c3c1ea5c coin control with multiple wallets.
laanwj
commented at 10:36 am on May 15, 2020:
member
ACK245c862cfd4883ea91b53d766abb00a9c3c1ea5c
MarcoFalke
commented at 11:54 am on May 15, 2020:
member
ACK245c862cfd solved the conflicts myself as a sanity check. Did not re-review 🍷
Signature:
0-----BEGIN PGP SIGNED MESSAGE-----
1Hash: SHA512
2 3ACK245c862cfd solved the conflicts myself as a sanity check. Did not re-review 🍷
4-----BEGIN PGP SIGNATURE-----
5 6iQGzBAEBCgAdFiEE+rVPoUahrI9sLGYTzit1aX5ppUgFAlwqrYAACgkQzit1aX5p
7pUg6kAv+LDQjoobwSPeclwoi0n8WEWBicnOXv7gq2Y9Iyq/bMkCuhHAzUev8NgNJ
8KsTf/TH40c526SEwA8bQiVWYgCvdJPgvWo7IQumU4eZOZjNoGt/CvUdUgACuFYSP
9FsrG4fsbA93BF/P/d+c2DmcHoDR2/ZSuJgrJaE1yRedEUEgO5haMjioxz6y6Oais
10/PXv37CYeV6TFF6hEf+l+7IcAKN1eWeMAGE0g5MhOhhPihSZPU6KNUUUkt0F/IK7
11tZuT2w3uk55QV7+zfLbZhOXgDf1gh9I4WaUpQwfg0JPECxmvO00aIGx9ytPg/iKQ
12H9Thom7whQw124Y6+rmfni3cahmo1pwIXMetLpKUQYQNNJun9BAlqTN/FSPhl4e4
13TcFEU9h6JU9cpGII5eP+z/x3pKYF1tVI6FLSr9Ti0/ByXDtY/N+FMtzfpDShg3KH
14IcO+/6yJ4O/SH5EOBEmJtcPnoCmueKEiBPydjxrbXbtsVrNqyvzkkaE0N+IyFGG/
1599TG/H6V
16=sXf4
17-----END PGP SIGNATURE-----
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: 2024-11-21 12:12 UTC
This site is hosted by @0xB10C More mirrored repositories can be found on mirror.b10c.me