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
<GitHub> [artiq] sbourdeauducq commented on issue #670: @webstersc Thanks for the report, but please create a new issue for new problems. https://github.com/m-labs/artiq/issues/670#issuecomment-292696216
<GitHub> [artiq] sbourdeauducq opened issue #705: "failed to create process" on Windows https://github.com/m-labs/artiq/issues/705
<GitHub> [artiq] sbourdeauducq commented on issue #705: Doing this and crossing my fingers that no regressions have been introduced ...... https://github.com/m-labs/artiq/issues/705#issuecomment-292696261
<sb0> bb-m-labs, force build artiq
<bb-m-labs> build forced [ETA 39m58s]
<bb-m-labs> I'll give a shout when the build finishes
<sb0> bb-m-labs, stop build artiq wrong vm
<bb-m-labs> build 1450 interrupted
<bb-m-labs> build #1450 of artiq is complete: Exception [exception interrupted] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1450
<GitHub> [artiq] sbourdeauducq commented on issue #704: @npisenti With pyqtgraph from pip, does the image applet exit cleanly? This patch was required: https://github.com/m-labs/pyqtgraph/commit/7d34e22da900e07d9d9d6009fc4bc1e91c4ac9a5 https://github.com/m-labs/artiq/issues/704#issuecomment-292696644
<sb0> bb-m-labs, force build artiq
<bb-m-labs> build forced [ETA 39m58s]
<bb-m-labs> I'll give a shout when the build finishes
<mithro> sb0: It doesn't look like the exception vector base is enabled on mor1k? Does the bios do some type of exception forwarding?
<GitHub> [artiq] sbourdeauducq commented on issue #704: @npisenti Well, this particular bug does seem fixed in 0.10 (https://github.com/pyqtgraph/pyqtgraph/blob/1426e334e1d20542400d77c72c132b04c6d17ddb/pyqtgraph/imageview/ImageView.py#L396). Can you try other applets, try to break them, and make sure that they behave? https://github.com/m-labs/artiq/issues/704#issuecomment-292696888
<sb0> mithro, the bios doesn't do exception forwarding
<mithro> sb0: How does exceptions/interrupts work under misoc+or1k then?
<mithro> Oh
<mithro> EVBAR is enable
<mithro> mor1kx/verilog/rtl/verilog/mor1kx_ctrl_cappuccino.v: .FEATURE_EVBAR ("ENABLED")
<mithro> mor1kx/verilog/rtl/verilog/mor1kx_cfgrs.v: parameter FEATURE_EVBAR = "NONE",
<bb-m-labs> build #510 of artiq-board is complete: Failure [failed anaconda_upload] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/510
<bb-m-labs> build #1451 of artiq is complete: Failure [failed anaconda_upload anaconda_upload_1] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1451
<GitHub> [artiq] sbourdeauducq commented on issue #705: > no regressions have been introduced... https://github.com/m-labs/artiq/issues/705#issuecomment-292697863
bb-m-labs has quit [Quit: buildmaster reconfigured: bot disconnecting]
bb-m-labs has joined #m-labs
<GitHub35> [buildbot-config] sbourdeauducq pushed 1 new commit to master: https://git.io/vSrxB
<GitHub35> buildbot-config/master 7e0d518 Sebastien Bourdeauducq: Revert "work around new conda-build output name bug"...
<sb0> bb-m-labs, force build artiq
<bb-m-labs> build #1452 forced
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #511 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/511
<bb-m-labs> build #1452 of artiq is complete: Failure [failed python_unittest_2] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1452
rohitksingh has joined #m-labs
<GitHub> [artiq] jordens opened issue #706: constant folding is inaccurate https://github.com/m-labs/artiq/issues/706
<rjo> whitequark, sb0: were there changes to RTIO recently? it seems to me that delays are to large by a factor of ref_multiplier. i.e. fine TS and coarse TX mixup, i.e. delay(16*us)==delay_mu(16000) is 128 µs long. have you looked at scope traces recently?
<GitHub> [artiq] jordens opened issue #707: prefix git tags with "release-" https://github.com/m-labs/artiq/issues/707
<GitHub> [artiq] jordens force-pushed pdq2 from 3790495 to 9f94202: https://github.com/m-labs/artiq/commits/pdq2
<GitHub> artiq/pdq2 e59c344 Robert Jordens: pdq2: crc/frame register accessors
<GitHub> artiq/pdq2 8992744 Robert Jordens: doc: pdq2 spi backend
<GitHub> artiq/pdq2 9d0efd7 Robert Jordens: pdq2: config writes
<rjo> and something else has changed in RTIO in the last ~10 days. now i am not seeing any events output...
<whitequark> rjo: that's interesting
<whitequark> regarding the ref_multiplier, no, I can't imagine any change that would cause that
<whitequark> regarding not seeing any events, there have been a few
<whitequark> sec
<whitequark> there's csr::cri_con::selected_write(0);
<whitequark> but it should be in that state by default
<GitHub> [artiq] whitequark commented on issue #707: OK but then we should rename `release-2` to at least `release-2.x` so that people don't get confused. Because if I can check out `release-2` and `release-2.0` that *is* confusing.... https://github.com/m-labs/artiq/issues/707#issuecomment-292705508
<GitHub> [artiq] jordens commented on issue #707: Ack. I don't think it gets confused by that branch vs tag. But will check. https://github.com/m-labs/artiq/issues/707#issuecomment-292707802
_whitelogger has joined #m-labs
rohitksingh has quit [Read error: Connection reset by peer]
rohitksingh has joined #m-labs
rohitksingh has quit [Ping timeout: 240 seconds]
rohitksingh has joined #m-labs
<sb0> rjo, i've been modifying rtio for drtio and dma, yes
<sb0> but I did look at the signals at the output of the board and didn't notice any obvious problem
<sb0> also, such a major timing problem would also show in the pulse rate test
<sb0> rjo, what target are you using?
rohitksingh1 has joined #m-labs
rohitksingh has quit [Ping timeout: 240 seconds]
<GitHub> [artiq] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/f314f8b8f59f41816c7b43882d20eb395c7796ae
<GitHub> artiq/master f314f8b Sebastien Bourdeauducq: relax test_rpc_timing
<rjo> sb0: it's not systematiccally everything. i am trying to narrow it down. it's on my kc705_sma_spi target which is otherwise nist_clock
mumptai has joined #m-labs
<bb-m-labs> build #512 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/512
<bb-m-labs> build #455 of artiq-win64-test is complete: Warnings [warnings python_unittest] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/455 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<bb-m-labs> build #1453 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1453
<GitHub> [artiq] sbourdeauducq commented on issue #705: Fixed this, but the original bug is still present. https://github.com/m-labs/artiq/issues/705#issuecomment-292724881
rohitksingh1 has quit [Quit: Leaving.]
rohitksingh has joined #m-labs
rohitksingh has quit [Quit: Leaving.]
<GitHub> [artiq] jordens commented on issue #707: I would also voted for vX.Y but that seems to pollute the namespace a bit too much. https://github.com/m-labs/artiq/issues/707#issuecomment-292738405
<GitHub> [artiq] whitequark commented on issue #707: `vX.Y` is great but I believe that this issue exists precisely because versioneer cannot cope with the `v` prefix. I.e. it treats anything starting with `v` (say, a branch called "virtual") as a release, and then breaks in an obscure way. https://github.com/m-labs/artiq/issues/707#issuecomment-292738486
<GitHub> [artiq] whitequark commented on issue #707: Arguably versioneer should be fixed. https://github.com/m-labs/artiq/issues/707#issuecomment-292738495
_whitelogger has joined #m-labs
Gurty has quit [Ping timeout: 240 seconds]
Gurty has joined #m-labs
Gurty has joined #m-labs
Gurty has quit [Changing host]