--- Log opened Wed Jul 20 00:00:26 2022
01:52 -!- gribble [~gribble@bitcoin/bot/gribble] has quit [Remote host closed the connection]
01:53 -!- darosior6 [~darosior@194.36.189.246] has joined #bitcoin-core-builds
01:54 -!- koolazer [~koo@user/koolazer] has quit [Ping timeout: 256 seconds]
01:54 -!- darosior [~darosior@194.36.189.246] has quit [Ping timeout: 256 seconds]
01:54 -!- darosior6 is now known as darosior
01:56 -!- koolazer [~koo@user/koolazer] has joined #bitcoin-core-builds
01:57 -!- gribble [~gribble@bitcoin/bot/gribble] has joined #bitcoin-core-builds
02:18 -!- gribble [~gribble@bitcoin/bot/gribble] has quit [Remote host closed the connection]
02:23 -!- gribble [~gribble@bitcoin/bot/gribble] has joined #bitcoin-core-builds
08:58 -!- MacroFake [~none@72.5.34.65] has joined #bitcoin-core-builds
09:32 -!- vasild [~vd@user/vasild] has quit [Remote host closed the connection]
09:33 -!- vasild [~vd@user/vasild] has joined #bitcoin-core-builds
10:02 -!- michaelfolkson2 is now known as michaelfolkson
11:52 < real_or_random> We just got this report about a CI failure in Core's CI in secp256k1 config... https://github.com/bitcoin-core/secp256k1/issues/1127 it's related to autoconf caching and I have no idea about this. Can one of you have a look?
12:02 < hebasto> real_or_random: looking...
15:00 -!- vasild [~vd@user/vasild] has quit [Remote host closed the connection]
15:05 -!- vasild [~vd@user/vasild] has joined #bitcoin-core-builds
18:43 -!- cfields_ [~cfields@user/cfields] has quit [Ping timeout: 256 seconds]
18:58 -!- cfields [~cfields@user/cfields] has joined #bitcoin-core-builds
20:11 -!- greypw254600 [~greypw254@grey.pw] has joined #bitcoin-core-builds
21:05 -!- david-bakin [~david-bak@c-174-61-163-5.hsd1.wa.comcast.net] has quit [Ping timeout: 240 seconds]
22:36 -!- ghost43_ [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
22:36 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-builds
--- Log closed Thu Jul 21 00:00:27 2022