--- Log opened Wed Jun 19 00:00:29 2024 01:19 -!- jon_atack [~jonatack@user/jonatack] has joined #bitcoin-core-builds 01:20 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 255 seconds] 01:20 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-builds 01:23 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 246 seconds] 02:15 -!- jon_atack [~jonatack@user/jonatack] has joined #bitcoin-core-builds 02:16 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 268 seconds] 02:19 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-builds 02:19 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 268 seconds] 02:34 < maxedw> I've seen it complain about the IPV6 docker network already existing. Do you think there needs to be a fix for that? 02:52 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 264 seconds] 02:54 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-builds 02:58 -!- jon_atack [~jonatack@user/jonatack] has joined #bitcoin-core-builds 03:00 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 252 seconds] 03:15 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-builds 03:15 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 252 seconds] 03:23 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 256 seconds] 03:23 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-builds 03:41 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 256 seconds] 03:42 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-builds 03:43 -!- jonatack [~jonatack@user/jonatack] has quit [Excess Flood] 03:44 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-builds 03:54 -!- pablomartin [~pablomart@194.35.123.48] has joined #bitcoin-core-builds 03:54 -!- jon_atack [~jonatack@user/jonatack] has joined #bitcoin-core-builds 03:55 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 272 seconds] 04:08 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-builds 04:10 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 272 seconds] 04:22 -!- kenzsad4869 [~kenzsad48@113.191.115.150] has joined #bitcoin-core-builds 04:24 -!- vasild [~vd@user/vasild] has quit [Ping timeout: 260 seconds] 04:26 -!- vasild [~vd@user/vasild] has joined #bitcoin-core-builds 04:27 -!- kenzsad4869 [~kenzsad48@113.191.115.150] has quit [Client Quit] 04:43 -!- josie_ [~josibake@suhail.uberspace.de] has joined #bitcoin-core-builds 04:44 -!- josie [~josibake@2a00:d0c0:200:3:ccd:dff:fec0:d062] has quit [Ping timeout: 268 seconds] 04:48 -!- jon_atack [~jonatack@user/jonatack] has joined #bitcoin-core-builds 04:50 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 272 seconds] 04:55 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-builds 04:57 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 264 seconds] 05:30 -!- jonatack [~jonatack@user/jonatack] has quit [Read error: Connection reset by peer] 05:30 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-builds 05:52 -!- pablomartin [~pablomart@194.35.123.48] has quit [Ping timeout: 268 seconds] 06:33 -!- pablomartin [~pablomart@194.35.123.37] has joined #bitcoin-core-builds 06:55 -!- jon_atack [~jonatack@user/jonatack] has joined #bitcoin-core-builds 06:57 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 252 seconds] 07:09 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-builds 07:11 < vasild> What if one wants to build normal debug build with cmake + the fuzz, should then two separate build directories be used? 07:11 < vasild> that is - compile both -DENABLE_FUZZ=OFF and -DENABLE_FUZZ=ON 07:11 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 268 seconds] 07:13 < hebasto> `-DENABLE_FUZZ=ON` disables all other targets and forces `BUILD_FUZZ_BINARY=ON` 07:14 < vasild> yes, I know 07:15 < hebasto> well, then I didn't get your q 07:15 < vasild> it is kind of obvious, but I am asking anyway, just to double check - then I need two separate build directories 07:15 < vasild> ? 07:16 < vasild> if I want to use both src/bitcoind and src/test/fuzz/fuzz at the same time 07:16 < hebasto> don't use `-DENABLE_FUZZ=ON`, just provide `-DBUILD_FUZZ_BINARY=ON` 07:17 < hebasto> does it work for you? 07:17 < vasild> hmm, but then would src/test/fuzz/fuzz be fully operational? 07:19 < hebasto> as far as I can tell, the difference will be in `ABORT_ON_FAILED_ASSUME` macro 07:24 < vasild> even that should be the same because of -DCMAKE_BUILD_TYPE=Debug, no? 07:25 < vasild> trying now -DCMAKE_BUILD_TYPE=Debug -DBUILD_FUZZ_BINARY=ON -DENABLE_FUZZ=OFF ... 07:28 < vasild> it does not work: `FUZZ=addrman ./src/test/fuzz/fuzz` hangs and prints nothing 07:30 -!- pablomartin4btc [~pablomart@89.37.175.4] has joined #bitcoin-core-builds 07:31 -!- pablomartin [~pablomart@194.35.123.37] has quit [Ping timeout: 268 seconds] 07:53 < hebasto> did you forget to pass a path to `qa-assets` directory? 07:54 < hebasto> `env FUZZ=addrman ./build/src/test/fuzz/fuzz qa-assets` returns `addrman: succeeded against 4 files in 0s.` 08:00 < vasild> it should start fuzzing even without the qa-assets directory, something is odd - it behaves the same even if I just use -DENABLE_FUZZ=ON ... 08:01 < hebasto> do you refer to the behavior on the master branch? 08:02 < vasild> yes, and IIRC I also played with the fuzzing when compiled with cmake 08:58 < vasild> hebasto: I have forgotten to add -DSANITIZERS=fuzzer,integer,undefined 09:03 -!- dergoegge [sid453889@id-453889.lymington.irccloud.com] has joined #bitcoin-core-builds 09:25 -!- pablomartin4btc_ [~pablomart@89.37.175.4] has joined #bitcoin-core-builds 09:27 -!- pablomartin4btc [~pablomart@89.37.175.4] has quit [Read error: Connection reset by peer] 10:15 -!- pablomartin4btc_ [~pablomart@89.37.175.4] has quit [Ping timeout: 240 seconds] 10:17 -!- lbia [~lbia@user/lbia] has quit [Ping timeout: 252 seconds] 11:15 -!- jon_atack [~jonatack@user/jonatack] has joined #bitcoin-core-builds 11:15 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 264 seconds] 11:40 -!- gribble [~gribble@bitcoin/bot/gribble] has quit [Remote host closed the connection] 11:46 -!- gribble [~gribble@bitcoin/bot/gribble] has joined #bitcoin-core-builds 11:47 -!- lbia [~lbia@user/lbia] has joined #bitcoin-core-builds 12:05 -!- pablomartin [~pablomart@185.216.146.90] has joined #bitcoin-core-builds 12:15 -!- jamesob [~jamesob@108.44.248.162] has quit [Ping timeout: 252 seconds] 14:19 -!- pablomartin [~pablomart@185.216.146.90] has quit [Ping timeout: 240 seconds] 14:45 -!- lbia [~lbia@user/lbia] has quit [Ping timeout: 255 seconds] 14:48 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-builds 14:49 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 255 seconds] 15:47 -!- lbia [~lbia@user/lbia] has joined #bitcoin-core-builds 16:04 -!- lbia [~lbia@user/lbia] has quit [Ping timeout: 255 seconds] 16:27 -!- lbia [~lbia@user/lbia] has joined #bitcoin-core-builds 22:01 < vasild> Proposed topic for today's CMake meeting: Problem: the current coverage that is integrated into the build system (cmake/script/Coverage*) is GCC/GCOV-centric. If the compiler is Clang it can produce better results if it uses the Clang native workflow. So, the question: How to integrate the Clang code coverage gathering. It boils down to https://github.com/vasild/bitcoin/wiki/Clang-code-coverage --- Log closed Thu Jun 20 00:00:30 2024