--- Log opened Mon Jun 22 00:00:37 2020 --- Day changed Mon Jun 22 2020 00:00 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev 00:02 -!- S3RK [~s3rk@47.246.66.115] has quit [Ping timeout: 265 seconds] 00:04 -!- yancy [~root@li1543-67.members.linode.com] has joined #bitcoin-core-dev 00:07 -!- marcoagner [~user@81.193.76.62] has joined #bitcoin-core-dev 00:11 -!- Pavlenex [~Thunderbi@185.189.114.187] has joined #bitcoin-core-dev 00:19 -!- S3RK [~s3rk@47.246.66.115] has joined #bitcoin-core-dev 00:19 -!- Pavlenex [~Thunderbi@185.189.114.187] has quit [Quit: Pavlenex] 00:47 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 00:47 < bitcoin-git> [bitcoin] D4nte opened pull request #19349: doc: Include wallet path to relevant RPC calls (master...doc-wallet) https://github.com/bitcoin/bitcoin/pull/19349 00:47 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 00:48 -!- dr-orlovsky [~dr-orlovs@xdsl-188-154-186-21.adslplus.ch] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 00:50 -!- Pavlenex [~Thunderbi@185.189.114.187] has joined #bitcoin-core-dev 00:52 -!- dr-orlovsky [~dr-orlovs@xdsl-188-154-186-21.adslplus.ch] has joined #bitcoin-core-dev 00:56 -!- S3RK [~s3rk@47.246.66.115] has quit [Remote host closed the connection] 00:56 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 260 seconds] 00:56 -!- S3RK [~s3rk@47.246.66.115] has joined #bitcoin-core-dev 00:57 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 260 seconds] 01:00 -!- S3RK [~s3rk@47.246.66.115] has quit [Ping timeout: 240 seconds] 01:04 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Ping timeout: 264 seconds] 01:06 -!- Guyver2 [Guyver@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 01:09 -!- S3RK [~s3rk@47.246.66.115] has joined #bitcoin-core-dev 01:38 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev 01:46 -!- shesek [~shesek@5.102.255.210] has joined #bitcoin-core-dev 01:46 -!- shesek [~shesek@5.102.255.210] has quit [Changing host] 01:46 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 01:59 -!- jonatack [~jon@184.75.221.179] has joined #bitcoin-core-dev 02:00 -!- brrr [~brrr@89.47.234.28] has quit [] 02:11 -!- Pavlenex [~Thunderbi@185.189.114.187] has quit [Quit: Pavlenex] 02:17 -!- belcher [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev 02:22 -!- bshum1 [~bshum@84.39.116.180] has joined #bitcoin-core-dev 02:42 -!- rjected [~dan@pool-71-184-77-198.bstnma.fios.verizon.net] has joined #bitcoin-core-dev 02:44 -!- S3RK [~s3rk@47.246.66.115] has quit [Remote host closed the connection] 02:44 -!- S3RK [~s3rk@47.246.66.115] has joined #bitcoin-core-dev 02:45 < vasild> How to observe debug.log after a run of test_bitcoin? It gets deleted at the end of the execution. To see what is inside I did run it inside gdb, set a breakpoint in unlink and when it stops at the breakpoint: cat /tmp/test_common_Bitcoin\ Core/*/debug.log 02:47 < vasild> "test_bitcoin -- -debuglogfile=/dev/stdout" did not print the log on the screen, nor did -printtoconsole=1 02:58 -!- Deinogalerix21 [~Deinogale@185.125.207.151] has joined #bitcoin-core-dev 03:01 -!- promag [~promag@bl19-22-20.dsl.telepac.pt] has quit [Remote host closed the connection] 03:02 -!- Deinogalerix21 [~Deinogale@185.125.207.151] has quit [Client Quit] 03:03 -!- Natasha80Jaskols [~Natasha80@static.57.1.216.95.clients.your-server.de] has joined #bitcoin-core-dev 03:08 -!- Natasha80Jaskols [~Natasha80@static.57.1.216.95.clients.your-server.de] has quit [Ping timeout: 265 seconds] 03:24 -!- Pavlenex [~Thunderbi@185.189.114.187] has joined #bitcoin-core-dev 03:27 -!- sipsorcery [~sipsorcer@37.228.243.107] has quit [Ping timeout: 256 seconds] 03:32 -!- Pavlenex [~Thunderbi@185.189.114.187] has quit [Quit: Pavlenex] 03:32 -!- Pavlenex [~Thunderbi@185.189.114.187] has joined #bitcoin-core-dev 03:32 -!- Pavlenex [~Thunderbi@185.189.114.187] has quit [Client Quit] 03:46 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev 03:46 < bitcoin-git> [bitcoin] ccdle12 opened pull request #19350: test: Refactor tests using restart_node (master...test-refactor-restart-node) https://github.com/bitcoin/bitcoin/pull/19350 03:46 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev [] 04:02 -!- promag [~promag@Bl19-22-20.dsl.telepac.pt] has joined #bitcoin-core-dev 04:17 -!- dr-orlovsky [~dr-orlovs@xdsl-188-154-186-21.adslplus.ch] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 04:29 -!- S3RK [~s3rk@47.246.66.115] has quit [Remote host closed the connection] 04:29 -!- S3RK [~s3rk@47.246.66.115] has joined #bitcoin-core-dev 04:33 -!- S3RK [~s3rk@47.246.66.115] has quit [Ping timeout: 246 seconds] 04:38 -!- kljasdfvv [~flack@p200300d46f11fb00c0115a766b4c6af2.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 04:44 < jonatack> vasild: for temporary printing with unit tests, so far i've managed with std::cout or std::cerr or BOOST_TEST_MESSAGE() combined with running the tests with --log_level=all 04:45 < vasild> jonatack: right, I also use printf() or std::cout sometimes, but some stuff is printed to debug.log by non-test code and I was wondering if that can be observed 04:46 < jonatack> yes, sorry, just realised i didn't answer your question 04:46 < vasild> I vaguely remember some --dont-remove-logs-at-the-end option, but maybe it was in some different software :) 04:47 < fanquake> vaslid: can you use --log_sink=stdout? 04:47 < vasild> trying... 04:48 -!- Mercury_Vapor [~Mercury_V@174-082-166-092.res.spectrum.com] has joined #bitcoin-core-dev 04:49 < fanquake> You can also control verbosity with --log_level. Anything between 'all' and 'nothing' 04:50 < fanquake> Quite a lot of info in --help if you haven't looked through it already 04:50 -!- Relis [~Relis@cpc96290-lewi18-2-0-cust910.2-4.cable.virginm.net] has joined #bitcoin-core-dev 04:50 < jonatack> yes, the help is good, as well as the details of --help=