✅ achow101 closed an issue: "test: Add TestNode wait_until helper"
(https://github.com/bitcoin/bitcoin/issues/29029)
(https://github.com/bitcoin/bitcoin/issues/29029)
🤔 furszy reviewed a pull request: "fuzz: coinselection, improve `min_viable_change`/`change_output_size`"
(https://github.com/bitcoin/bitcoin/pull/28372#pullrequestreview-1782561357)
Left a comment
(https://github.com/bitcoin/bitcoin/pull/28372#pullrequestreview-1782561357)
Left a comment
💬 furszy commented on pull request "fuzz: coinselection, improve `min_viable_change`/`change_output_size`":
(https://github.com/bitcoin/bitcoin/pull/28372#discussion_r1427177813)
> This will narrow down the range of output sizes being fuzzed.
Agree.
You don't need to create valid known destinations, we only care about the change output size. All yours:
```diff
diff --git a/src/wallet/test/fuzz/coinselection.cpp b/src/wallet/test/fuzz/coinselection.cpp
--- a/src/wallet/test/fuzz/coinselection.cpp (revision ccb25a1ddc1f79f432a6718604f01ed97dced15f)
+++ b/src/wallet/test/fuzz/coinselection.cpp (date 1702581796902)
@@ -11,6 +11,7 @@
#include <test/util/setup_commo
...
(https://github.com/bitcoin/bitcoin/pull/28372#discussion_r1427177813)
> This will narrow down the range of output sizes being fuzzed.
Agree.
You don't need to create valid known destinations, we only care about the change output size. All yours:
```diff
diff --git a/src/wallet/test/fuzz/coinselection.cpp b/src/wallet/test/fuzz/coinselection.cpp
--- a/src/wallet/test/fuzz/coinselection.cpp (revision ccb25a1ddc1f79f432a6718604f01ed97dced15f)
+++ b/src/wallet/test/fuzz/coinselection.cpp (date 1702581796902)
@@ -11,6 +11,7 @@
#include <test/util/setup_commo
...
💬 theuni commented on pull request "[WIP, DO NOT MERGE!!11111!!!!!] build: Require libc++-16 or later":
(https://github.com/bitcoin/bitcoin/pull/29077#discussion_r1427188598)
More missing in v10: https://github.com/bitcoin/bitcoin/pull/29081#issuecomment-1856419623
(https://github.com/bitcoin/bitcoin/pull/29077#discussion_r1427188598)
More missing in v10: https://github.com/bitcoin/bitcoin/pull/29081#issuecomment-1856419623
⚠️ LeoSpyke opened an issue: "test: feature_index_prune.py timeout failure"
(https://github.com/bitcoin/bitcoin/issues/29082)
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current behaviour
The `test/functional/test_runner.py --extended --jobs=8` command raises an `AssertionError: Block sync timed out after 60s` when running the `feature_index_prune.py` suite.
Also tried with `--jobs=4`.
Very similar to #27091.
### Expected behaviour
I expected the test to complete successfully.
### Steps to reproduce
```bash
git clone https://github.com/bitcoin/bitcoin
# instal
...
(https://github.com/bitcoin/bitcoin/issues/29082)
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current behaviour
The `test/functional/test_runner.py --extended --jobs=8` command raises an `AssertionError: Block sync timed out after 60s` when running the `feature_index_prune.py` suite.
Also tried with `--jobs=4`.
Very similar to #27091.
### Expected behaviour
I expected the test to complete successfully.
### Steps to reproduce
```bash
git clone https://github.com/bitcoin/bitcoin
# instal
...
💬 maflcko commented on issue "test: `feature_index_prune.py` timeout failure":
(https://github.com/bitcoin/bitcoin/issues/29082#issuecomment-1856485017)
Does it pass if you increase the timeout factor? See `./test/functional/test_runner.py --help | grep factor`?
(https://github.com/bitcoin/bitcoin/issues/29082#issuecomment-1856485017)
Does it pass if you increase the timeout factor? See `./test/functional/test_runner.py --help | grep factor`?
💬 RandyMcMillan commented on pull request "Make provably unsignable standard P2PK and P2MS outpoints unspendable.":
(https://github.com/bitcoin/bitcoin/pull/28400#issuecomment-1856492483)
Concept ACK
(https://github.com/bitcoin/bitcoin/pull/28400#issuecomment-1856492483)
Concept ACK
⚠️ sarthak13gupta opened an issue: "Not able to build and compile on macos"
(https://github.com/bitcoin/bitcoin/issues/29083)
Hey there , I'm facing these issues.
I ran these commands
`./autogen.sh`
`./configure --disable-bench --disable-fuzz-binary --enable-debug --without-gui --enable-suppress-external-warnings`
` make`
<img width="1440" alt="Screenshot 2023-12-15 at 1 02 35 AM" src="https://github.com/bitcoin/bitcoin/assets/74540123/8d96fcda-36c0-4a06-934f-a83e9a96b543">
<img width="1434" alt="Screenshot 2023-12-15 at 1 02 48 AM" src="https://github.com/bitcoin/bitcoin/assets/74540123/0656acd4
...
(https://github.com/bitcoin/bitcoin/issues/29083)
Hey there , I'm facing these issues.
I ran these commands
`./autogen.sh`
`./configure --disable-bench --disable-fuzz-binary --enable-debug --without-gui --enable-suppress-external-warnings`
` make`
<img width="1440" alt="Screenshot 2023-12-15 at 1 02 35 AM" src="https://github.com/bitcoin/bitcoin/assets/74540123/8d96fcda-36c0-4a06-934f-a83e9a96b543">
<img width="1434" alt="Screenshot 2023-12-15 at 1 02 48 AM" src="https://github.com/bitcoin/bitcoin/assets/74540123/0656acd4
...
💬 maflcko commented on issue "Not able to build and compile on macos":
(https://github.com/bitcoin/bitcoin/issues/29083#issuecomment-1856500865)
Did you run `make clean`?
(https://github.com/bitcoin/bitcoin/issues/29083#issuecomment-1856500865)
Did you run `make clean`?
💬 achow101 commented on pull request "Get rid of shutdown.cpp/shutdown.h, use SignalInterrupt directly":
(https://github.com/bitcoin/bitcoin/pull/28051#issuecomment-1856505048)
ACK 6db04be102807ee0120981a9b8de62a55439dabb
Code seems fine, but I'm not familiar enough with this area to say whether this is the right approach or if there are any side effects that haven't been thought of.
(https://github.com/bitcoin/bitcoin/pull/28051#issuecomment-1856505048)
ACK 6db04be102807ee0120981a9b8de62a55439dabb
Code seems fine, but I'm not familiar enough with this area to say whether this is the right approach or if there are any side effects that haven't been thought of.
💬 sarthak13gupta commented on issue "Not able to build and compile on macos":
(https://github.com/bitcoin/bitcoin/issues/29083#issuecomment-1856510625)
Yes I have tried that.
(https://github.com/bitcoin/bitcoin/issues/29083#issuecomment-1856510625)
Yes I have tried that.
💬 maflcko commented on issue "Not able to build and compile on macos":
(https://github.com/bitcoin/bitcoin/issues/29083#issuecomment-1856514195)
What is your operating system and architecture? Where did you get BDB from?
(https://github.com/bitcoin/bitcoin/issues/29083#issuecomment-1856514195)
What is your operating system and architecture? Where did you get BDB from?
💬 maflcko commented on issue "Not able to build and compile on macos":
(https://github.com/bitcoin/bitcoin/issues/29083#issuecomment-1856514918)
Do you need BDB? If not, you can disable it with `--without-bdb`.
(https://github.com/bitcoin/bitcoin/issues/29083#issuecomment-1856514918)
Do you need BDB? If not, you can disable it with `--without-bdb`.
💬 hebasto commented on issue "Not able to build and compile on macos":
(https://github.com/bitcoin/bitcoin/issues/29083#issuecomment-1856517075)
What is the `./configure` script summary?
(https://github.com/bitcoin/bitcoin/issues/29083#issuecomment-1856517075)
What is the `./configure` script summary?
💬 maflcko commented on pull request "fuzz: Improve fuzzing stability for minisketch harness":
(https://github.com/bitcoin/bitcoin/pull/29064#issuecomment-1856517924)
review ACK b2fc7a2eda103724ac8cbeaf99df3ce6f5b7d974
(https://github.com/bitcoin/bitcoin/pull/29064#issuecomment-1856517924)
review ACK b2fc7a2eda103724ac8cbeaf99df3ce6f5b7d974
🚀 achow101 merged a pull request: "Get rid of shutdown.cpp/shutdown.h, use SignalInterrupt directly"
(https://github.com/bitcoin/bitcoin/pull/28051)
(https://github.com/bitcoin/bitcoin/pull/28051)
👋 dergoegge's pull request is ready for review: "fuzz: Improve fuzzing stability for minisketch harness"
(https://github.com/bitcoin/bitcoin/pull/29064)
(https://github.com/bitcoin/bitcoin/pull/29064)
✅ LeoSpyke closed an issue: "test: `feature_index_prune.py` timeout failure"
(https://github.com/bitcoin/bitcoin/issues/29082)
(https://github.com/bitcoin/bitcoin/issues/29082)
💬 LeoSpyke commented on issue "test: `feature_index_prune.py` timeout failure":
(https://github.com/bitcoin/bitcoin/issues/29082#issuecomment-1856519929)
Setting `--timeout-factor=2` did the trick.
Thank you @maflcko.
(https://github.com/bitcoin/bitcoin/issues/29082#issuecomment-1856519929)
Setting `--timeout-factor=2` did the trick.
Thank you @maflcko.
⚠️ hebasto opened an issue: "`security-check.py` produces false positive result for stack smashing protection"
(https://github.com/bitcoin/bitcoin/issues/29084)
I'm aware that `test-security-check.py` tests both cases `-fno-stack-protector` and `-fstack-protector-all`.
However, the `security-check.py` passes in the master branch @ 986047170892c9482ccbc21f05bf4f1499b3089d with the diff as follows:
```diff
--- a/configure.ac
+++ b/configure.ac
@@ -935,7 +935,7 @@ fi
if test "$use_hardening" != "no"; then
use_hardening=yes
AX_CHECK_COMPILE_FLAG([-Wstack-protector], [HARDENED_CXXFLAGS="$HARDENED_CXXFLAGS -Wstack-protector"])
- AX_CHECK_CO
...
(https://github.com/bitcoin/bitcoin/issues/29084)
I'm aware that `test-security-check.py` tests both cases `-fno-stack-protector` and `-fstack-protector-all`.
However, the `security-check.py` passes in the master branch @ 986047170892c9482ccbc21f05bf4f1499b3089d with the diff as follows:
```diff
--- a/configure.ac
+++ b/configure.ac
@@ -935,7 +935,7 @@ fi
if test "$use_hardening" != "no"; then
use_hardening=yes
AX_CHECK_COMPILE_FLAG([-Wstack-protector], [HARDENED_CXXFLAGS="$HARDENED_CXXFLAGS -Wstack-protector"])
- AX_CHECK_CO
...