sb0 changed the topic of #m-labs to: ARTIQ, Migen, MiSoC, Mixxeo & other M-Labs projects :: fka #milkymist :: Logs http://irclog.whitequark.org/m-labs
<GitHub103> [sinara] gkasprow pushed 1 new commit to master: https://github.com/m-labs/sinara/commit/1cf5cf260af9c8a1bf2ba0740d0284c7a526d724
<GitHub103> sinara/master 1cf5cf2 Greg: Production ready - fixed #321 #278 #322
_whitelogger has joined #m-labs
<sb0> (timestamp - zt) is -4112, yet DMA still succeeds << what's in the analyzer?
<sb0> whitequark, in migen: sum(x[i] for i in len(x))
<sb0> *range(len(x))
rohitksingh_work has joined #m-labs
<sb0> bb-m-labs, force build --branch=rtio-sed artiq
<bb-m-labs> The build has been queued, I'll give a shout when it starts
<GitHub122> [artiq] sbourdeauducq pushed 1 new commit to rtio-sed: https://github.com/m-labs/artiq/commit/b772c2c2378861fe19cc9298a34cb5ad2ddc3d92
<GitHub122> artiq/rtio-sed b772c2c Sebastien Bourdeauducq: conda: update misoc
<sb0> whitequark, do you have a repro for the rtio counter bug? does it happen both on master and rtio-sed?
<bb-m-labs> build #590 of artiq-win64-test is complete: Failure [failed python_unittest conda_remove] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/590
<bb-m-labs> build #1716 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1716
<bb-m-labs> build forced [ETA 8h32m20s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #834 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/834
<bb-m-labs> build #1717 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1717
<sb0> bb-m-labs, force build --branch=rtio-sed artiq
<bb-m-labs> build forced [ETA 8h32m20s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #835 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/835
<bb-m-labs> build #1718 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1718
<GitHub56> [misoc] sbourdeauducq pushed 1 new commit to master: https://git.io/vdy5a
<GitHub56> misoc/master 362de1a Sebastien Bourdeauducq: try to unbreak conda
<bb-m-labs> build #264 of misoc is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/misoc/builds/264
Gurty has quit [Ping timeout: 255 seconds]
Gurty has joined #m-labs
<sb0> bb-m-labs, force build --branch=rtio-sed artiq
<bb-m-labs> build forced [ETA 8h32m20s]
<bb-m-labs> I'll give a shout when the build finishes
<GitHub150> [artiq] sbourdeauducq pushed 1 new commit to rtio-sed: https://github.com/m-labs/artiq/commit/acb25f549b2ebc6beb5f2251b83cabf389a8b414
<GitHub150> artiq/rtio-sed acb25f5 Sebastien Bourdeauducq: conda: use new misoc version number
Gurty has quit [Max SendQ exceeded]
Gurty has joined #m-labs
<bb-m-labs> build #836 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/836
<bb-m-labs> build #1719 of artiq is complete: Failure [failed python_unittest_2] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1719
<sb0> whitequark, ^ there are still dma underflow errors
<sb0> exactly the same as before
<sb0> have you tried building with ISE?
Gurty has quit [Ping timeout: 255 seconds]
<whitequark> sb0: these errors do not match what I observe locally
<whitequark> did tiy merge master into rtio-sed?
<whitequark> *did you
<rjo> whitequark: with those mor1kx changes, does the PCU work for you?
<GitHub113> [sinara] gkasprow pushed 1 new commit to master: https://github.com/m-labs/sinara/commit/ceecda2464c4097e43b9e7acf5e3cb2bb71e9356
<GitHub113> sinara/master ceecda2 Greg: pdf update
<whitequark> rjo: yes.
<whitequark> and the values seem OK to me.
rohitksingh_work has quit [Ping timeout: 240 seconds]
<sb0> whitequark, non I didn't merge
rohitksingh_work has joined #m-labs
<rjo> sb0: who did the mixxeo layout?
Gurty has joined #m-labs
rohitksingh_work has quit [Read error: Connection reset by peer]
<sb0> rjo, greg et al
<GitHub139> [nu-servo] jordens deleted dds at 6069361: https://github.com/m-labs/nu-servo/commit/6069361
ohama has quit [Ping timeout: 240 seconds]
ohama has joined #m-labs
<GitHub110> [nu-servo] jordens pushed 5 new commits to master: https://github.com/m-labs/nu-servo/compare/213e57cfdce6...13be9587d73e
<GitHub110> nu-servo/master 8993d37 Robert Jordens: adc: clarify, cleanup
<GitHub110> nu-servo/master 9f567e1 Robert Jordens: spi: add new spi driver
<GitHub110> nu-servo/master aba31cf Robert Jordens: adc: cleanup/rename
<GitHub21> [sinara] gkasprow pushed 1 new commit to master: https://github.com/m-labs/sinara/commit/ce8e79ab872f013e036ea29331545e6bd98477fc
<GitHub21> sinara/master ce8e79a Greg: fixed #336 #278 #274 #337 #335 Release candidate
<GitHub171> [artiq] cjbe opened issue #840: Frequent malformed packet errors https://github.com/m-labs/artiq/issues/840
<GitHub110> [artiq] whitequark commented on issue #840: I could log malformed packets so that it's easy to tell if they are benign or not. Your case is likely to be benign though, just some network background radiation. https://github.com/m-labs/artiq/issues/840#issuecomment-337403073