--- Log opened Thu May 21 00:00:29 2020
00:09 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 252 seconds]
00:10 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #bitcoin-builds
00:47 -!- hebasto [~hebasto@95.164.65.194] has quit [Ping timeout: 246 seconds]
00:50 -!- hebasto [~hebasto@95.164.65.194] has joined #bitcoin-builds
00:58 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 260 seconds]
00:59 -!- jonatack [~jon@37.170.253.61] has joined #bitcoin-builds
01:53 -!- jonatack_ [~jon@37.167.18.204] has joined #bitcoin-builds
01:57 -!- jonatack [~jon@37.170.253.61] has quit [Ping timeout: 256 seconds]
02:02 -!- jonatack_ [~jon@37.167.18.204] has quit [Quit: jonatack_]
02:02 -!- jonatack [~jon@37.167.18.204] has joined #bitcoin-builds
03:04 -!- Alda63Bednar [~Alda63Bed@static.57.1.216.95.clients.your-server.de] has joined #bitcoin-builds
06:06 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has quit [Remote host closed the connection]
06:17 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has joined #bitcoin-builds
08:21 < hebasto> dongcarl: hi! mind pushing your great #18820 from "draft" to "ready-to-review"? :)
08:21 < gribble> https://github.com/bitcoin/bitcoin/issues/18820 | build: Propagate well-known vars into depends by dongcarl · Pull Request #18820 · bitcoin/bitcoin · GitHub
08:26 -!- Alda63Bednar [~Alda63Bed@static.57.1.216.95.clients.your-server.de] has quit [Ping timeout: 260 seconds]
08:58 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-builds
11:53 < hebasto> MarcoFalke: I do not fully understand the evil of "double lock of a mutex" that ThreadSanitizer reports about. Googling didn't help also. Have you an opinion about degree of harm of such warnings?
11:54 < sipa> harm of double locking a mutex, or harm of warning about it?
11:55 < hebasto> non-recursive mutex couldn't be locked twice in a row, right? What exactly this warning is about?
11:59 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
12:01 < sipa> hebasto: it's not legal to lock a mutex you already hold
12:01 < sipa> (unless it's a recursive mutex)
12:01 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-builds
12:02 < hebasto> sure, so warning "double lock of a mutex" about non-recursive mutex is unclear for me
12:02 < sipa> i don't understand
12:02 < dongcarl> hebasto: Ah, will do. Let me investigate the failures first
12:02 < sipa> it's illegal, so why is warning bad about it?
12:17 -!- jonatack_ [~jon@184.75.221.203] has joined #bitcoin-builds
12:18 -!- jonatack [~jon@37.167.18.204] has quit [Ping timeout: 256 seconds]
12:23 -!- jonatack_ [~jon@184.75.221.203] has quit [Quit: jonatack_]
12:24 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #bitcoin-builds
21:30 -!- mol_ [~mol@unaffiliated/molly] has joined #bitcoin-builds
21:33 -!- molz_ [~mol@unaffiliated/molly] has quit [Ping timeout: 256 seconds]
23:23 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection]
23:23 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #bitcoin-builds
--- Log closed Fri May 22 00:00:28 2020