--- Log opened Tue Jun 18 00:00:28 2024
00:15 -!- vasild [~vd@user/vasild] has joined #bitcoin-core-builds
00:50 -!- jon_atack [~jonatack@user/jonatack] has joined #bitcoin-core-builds
00:53 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 256 seconds]
01:33 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-builds
01:35 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 255 seconds]
04:32 -!- jon_atack [~jonatack@user/jonatack] has joined #bitcoin-core-builds
04:34 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 256 seconds]
05:09 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-builds
05:10 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 246 seconds]
06:48 -!- dongcarl [~dongcarl@syn-066-065-169-019.res.spectrum.com] has quit [Ping timeout: 268 seconds]
06:51 -!- dongcarl [~dongcarl@syn-066-065-169-019.res.spectrum.com] has joined #bitcoin-core-builds
07:33 -!- jon_atack [~jonatack@user/jonatack] has joined #bitcoin-core-builds
07:35 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 256 seconds]
08:28 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 264 seconds]
08:31 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-builds
08:44 -!- jon_atack [~jonatack@user/jonatack] has joined #bitcoin-core-builds
08:44 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 252 seconds]
09:24 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 264 seconds]
09:25 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-builds
09:28 -!- jon_atack [~jonatack@user/jonatack] has joined #bitcoin-core-builds
09:29 < vasild> hebasto: wrt https://github.com/hebasto/bitcoin/pull/233#issuecomment-2176015070, what's the workflow of running tests when using "Ninja Multi-Config"? It should be the same.
09:30 < vasild> running the tests is the same regardless of whether compilation was done with coverage enabled or not
09:30 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 246 seconds]
09:31 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-builds
09:32 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 252 seconds]
09:37 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 252 seconds]
09:38 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-builds
10:56 -!- brunoerg_ [~brunoerg@2804:14c:3bfb:37:19b3:8ee7:8e32:110a] has joined #bitcoin-core-builds
11:00 -!- brunoerg [~brunoerg@2804:14c:3bfb:37:38b6:9afd:da22:684] has quit [Ping timeout: 255 seconds]
13:40 < maxedw> :maflcko have you seen the CI failures on Cirrus? Looks like one of the workers has got into a weird state.
13:40 < maxedw> here is an example: https://github.com/bitcoin/bitcoin/pull/30245/checks?check_run_id=26384459400
15:32 < maflcko> Should be fixed now
17:43 -!- jon_atack [~jonatack@user/jonatack] has joined #bitcoin-core-builds
17:44 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 264 seconds]
21:35 -!- vasild [~vd@user/vasild] has quit [Remote host closed the connection]
21:36 -!- vasild [~vd@user/vasild] has joined #bitcoin-core-builds
23:04 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-builds
23:04 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 264 seconds]
--- Log closed Wed Jun 19 00:00:29 2024