<GitHub51>
[migen] whitequark pushed 1 new commit to master: http://git.io/vuBnP
<GitHub51>
migen/master 110af84 whitequark: conda: use BUILDNUMBER from environment.
<GitHub197>
[misoc] whitequark pushed 1 new commit to master: http://git.io/vuBce
<GitHub197>
misoc/master 4786524 whitequark: conda: use BUILDNUMBER from environment.
<GitHub25>
[misoc] whitequark force-pushed master from 4786524 to 814435d: http://git.io/LjONPA
<GitHub25>
misoc/master 814435d whitequark: conda: use BUILDNUMBER from environment.
<GitHub181>
[migen] whitequark force-pushed master from 110af84 to b2eedfd: http://git.io/pZru
<GitHub181>
migen/master b2eedfd whitequark: conda: use BUILDNUMBER from environment.
<GitHub109>
[artiq] whitequark pushed 2 new commits to master: http://git.io/vuBWJ
<GitHub109>
artiq/master ff09a98 whitequark: conda: use BUILDNUMBER from environment.
<GitHub109>
artiq/master 07ef890 whitequark: conda: fix buildscripts to get bscan bitstreams correctly.
<whitequark>
sb0: ok, repeat builds will no longer fall over
<whitequark>
oh
<whitequark>
oh no they will
<whitequark>
god I hate this anaconda garbage
<whitequark>
so, what it does is it uses one field for dependency resolution, but another field for checking uniqueness of packages
<whitequark>
er, no
<whitequark>
it uses one field for determining the latest version during resolution, and another field for specifying dependencies and checking uniqueness of packages
<whitequark>
oh ffs I'll just do anaconda upload --force
<GitHub97>
[migen] whitequark pushed 1 new commit to master: http://git.io/vuBuX
<GitHub97>
migen/master 27b603e whitequark: Revert "conda: use BUILDNUMBER from environment."...
<GitHub139>
[misoc] whitequark pushed 1 new commit to master: http://git.io/vuBuy
<GitHub139>
misoc/master 2957ecf whitequark: Revert "conda: use BUILDNUMBER from environment."...
<GitHub42>
[artiq] whitequark pushed 1 new commit to master: http://git.io/vuBud
<GitHub42>
artiq/master 400999f whitequark: Revert "conda: use BUILDNUMBER from environment."...
bb-m-labs has quit [Quit: buildmaster reconfigured: bot disconnecting]
<rjo>
sb0: in migen.sim.core.Executor.run(), why are the generators processed after the sync statements? if i write "def sim(): yield a.eq(1); yield" i would expect the statement to execute before the (first) clock edge.
<rjo>
and thus before the sync statements in that cd are executed.
<rjo>
s/Executor/Simulator/
<rjo>
ah. the cd is executed but not yet committed.
mumptai has quit [Quit: Verlassend]
<rjo>
sb0: i suspect that list_targets() should generally return the actual slice that is affected. the reset for (potentially only partial) comb targets is indiscriminate.
aeris has quit [Read error: Connection reset by peer]