Jones42_ has quit [Read error: Connection reset by peer]
Kubu_work has quit [Quit: Leaving.]
enok has joined #yocto
Chaser has quit [Quit: My Unrecognized Mac has gone to sleep. ZZZzzz…]
enok has quit [Ping timeout: 248 seconds]
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #yocto
Ad0 has quit [Ping timeout: 260 seconds]
goliath has joined #yocto
Chaser has joined #yocto
Ad0 has joined #yocto
vthor has quit [Excess Flood]
vthor has joined #yocto
vthor has quit [Changing host]
vthor has joined #yocto
flom84 has joined #yocto
flom84 has quit [Ping timeout: 255 seconds]
sakoman has quit [Ping timeout: 248 seconds]
sugoi has joined #yocto
sugoi has quit [Ping timeout: 252 seconds]
sakoman has joined #yocto
Vonter has joined #yocto
marex_ is now known as marex
jmiehe has joined #yocto
vthor has quit [Quit: kill -9 $pid]
jmiehe has quit [Remote host closed the connection]
Chaser has quit [Quit: My Unrecognized Mac has gone to sleep. ZZZzzz…]
Chaser has joined #yocto
Chaser has quit [Quit: My Unrecognized Mac has gone to sleep. ZZZzzz…]
<yocton>
RP: khem: What do you think about making the reproducible test work even in case of a partially failed build? (ie: adding "--continue" to the bitbake cmdline)
<yocton>
That would let us see the reproducible state even in case of an unrelated build faillure
<yocton>
That shouldn't change much for oe-core, that would be most beneficial for the meta-oe tests
<RP>
yocton: I'm torn on it and I think I've gone back and forth on this. The trouble is if things don't build, the reproducibile result is inaccurate
<yocton>
Inaccurate as in "We don't see reproducible state for package that don't build"?
<RP>
yocton: imagine m4-native fails and then reproducibility passes since it didn't build anything
<yocton>
RP: I would ensure that the global build is only green for a successful build AND reproducible output
olani has joined #yocto
<RP>
yocton: what about the test result value in json though?
<yocton>
I'm not familiar with this one :-| I'll look into it