<d1b2>
<4o> that's a very soft bug report. i've been seeing such messages while pysim: "fakename:46: DriverConflict: Signal '(sig $signal)' is driven from multiple fragments: top.crc, top.rx_decoder; hierarchy will be flattened". restarting the sim fixes it
<whitequark[m]>
what is the bug?
<whitequark[m]>
i.e. what do you expect to happen and how does restarting the sim help?
<d1b2>
<4o> sim fails when this is reported. i'm running hundreds of unit tests in a batch. i see this like 1 time in ~10-20 runs so error rate <1/1000. dont have more info, just this symptom now. hard to get info as it's not that easy to reproduce
<whitequark[m]>
interesting
<whitequark[m]>
yes, that is definitely a bug
<whitequark[m]>
a small repro would be most welcome, even if it's not fully deterministic
<d1b2>
<4o> i'll try to pin it down
pftbest has joined #nmigen
pftbest has quit [Remote host closed the connection]
pftbest has joined #nmigen
emeb_mac has quit [Quit: Leaving.]
bvernoux has joined #nmigen
someone--else has joined #nmigen
someone--else has quit [Quit: Connection closed]
someone--else has joined #nmigen
emeb has joined #nmigen
pftbest has quit [Read error: Connection reset by peer]