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
<bb-m-labs> build #1150 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1150
<bb-m-labs> build #2005 of artiq is complete: Failure [failed artiq_flash] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2005 blamelist: whitequark <whitequark@whitequark.org>
marmelada has quit [Ping timeout: 260 seconds]
<bb-m-labs> build #240 of migen is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/migen/builds/240
rohitksingh-demo has joined #m-labs
jkeller has joined #m-labs
<jkeller> bb-m-labs: force build --props=package=artiq-kc705-nist_qc2 --branch=release-3 artiq-board
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build forced [ETA 19m52s]
rohitksingh-demo has quit [Client Quit]
<bb-m-labs> build #1151 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1151
jkeller has quit [Quit: Page closed]
<whitequark> sb0: did you do something to the sayma-amc gateware?
<whitequark> it used to compile in 20 minutes. now it compiles in a fuckton minutes.
<GitHub186> [artiq] whitequark commented on issue #898: @jbqubit ... https://github.com/m-labs/artiq/issues/898#issuecomment-360948881
<GitHub115> [artiq] whitequark commented on issue #898: @jbqubit ... https://github.com/m-labs/artiq/issues/898#issuecomment-360948881
<whitequark> sb0: on sayma-3, JTAG is not working again, even after resetting the boards, and on sayma-1 the firmware I flashed (freshly built) doens't boot BIOS
<whitequark> can you confirm?
<whitequark> I'll just keep using the kc705...
<sb0> whitequark, use --without-sawg
<sb0> what changed is it is enabled by default
<sb0> whitequark, I power-cycled the saymas and sayma-3 JTAG is working again. what exactly is the problem on sayma-1?
Jen_ has joined #m-labs
Jen_ has quit [Client Quit]
<GitHub160> [artiq] sbourdeauducq commented on issue #652: I don't know for how long Python 3.5 will keep working on conda. 32-bit Windows is already broken (which is why we no longer have ARTIQ packages for that OS). Not having Python 3.6 support may get the project stuck or requiring lots of conda workarounds. https://github.com/m-labs/artiq/issues/652#issuecomment-360952521
<GitHub162> [artiq] sbourdeauducq commented on issue #652: I don't know for how long Python 3.5 will keep working on conda. 32-bit Windows is already broken (which is why we no longer have ARTIQ packages for that OS). Not having Python 3.6 support (or in general, not tracking what everybody else is doing with conda) may get the project stuck or requiring lots of conda workarounds. https://github.com/m-labs/artiq/issues/652#
sb0 has quit [Quit: Leaving]
<GitHub197> [smoltcp] hjr3 commented on pull request #125 6a89a57: I imagine one would want to know the identifier of the unknown option too? https://github.com/m-labs/smoltcp/pull/125#discussion_r164260623
<GitHub38> [smoltcp] hjr3 commented on pull request #125 6a89a57: I imagine one would want to know the identifier of the unknown option too?... https://github.com/m-labs/smoltcp/pull/125#discussion_r164260623
<GitHub95> [artiq] sbourdeauducq commented on issue #908: What Vivado version? https://github.com/m-labs/artiq/issues/908#issuecomment-360956100
<GitHub12> [artiq] sbourdeauducq commented on issue #908: What Vivado version?... https://github.com/m-labs/artiq/issues/908#issuecomment-360956100
sb0 has joined #m-labs
sb0 has quit [Client Quit]
futarisIRCcloud has joined #m-labs
<GitHub41> [smoltcp] whitequark commented on pull request #125 6a89a57: Yeah, of course. https://github.com/m-labs/smoltcp/pull/125#discussion_r164269558
<whitequark> sb0: it doesn't boot. nothing on UART.
<whitequark> ok, it boots now.
<GitHub171> [smoltcp] LuoZijun opened pull request #135: Fix features dependencies (master...patch-2) https://github.com/m-labs/smoltcp/pull/135
sb0 has joined #m-labs
<GitHub185> [smoltcp] whitequark closed pull request #135: fix features dependencies (master...patch-2) https://github.com/m-labs/smoltcp/pull/135
<GitHub175> smoltcp/master f0c147a 寧靜: Gate Linux-specific platform dependencies behind a #[cfg].
<GitHub175> [smoltcp] whitequark pushed 1 new commit to master: https://github.com/m-labs/smoltcp/commit/f0c147a5ee163b5c26894ade28cb5c9f9588e69e
<GitHub188> [smoltcp] whitequark commented on issue #135: Thanks! By the way, can you please submit your OS X raw socket code as a PR? https://github.com/m-labs/smoltcp/pull/135#issuecomment-360982223
<travis-ci> m-labs/smoltcp#638 (master - f0c147a : 寧靜): The build passed.
<sb0> whitequark, any idea why the kc705 couldn't be flashed by the buildbot anymore? I power-cycled it, did that help?
<sb0> are you using the flash right now and is it working?
<sb0> the board is still booting...
<sb0> if it's a hardware issue I can swap it with the spare kc705 we have
rohitksingh-demo has joined #m-labs
<whitequark> yes I was using the board
<whitequark> well, I was holding the lock
<sb0> whitequark, look at the log - artiq_flash runs but fails to find the flash chip
rohitksingh-demo has quit [Quit: Leaving.]
<whitequark> oh
<whitequark> oh yeah I hit that too
<whitequark> I was about to start figuring that out but got distracted, actually
<whitequark> so it might be a hardware issue.
<whitequark> please look into it, I don't know.
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
<GitHub16> [artiq] gkasprow commented on issue #854: @sbourdeauducq I loaded the bit files @marmeladapk generated. And the Txclock is there, it looks good and the LINK is up. https://github.com/m-labs/artiq/issues/854#issuecomment-360986380
<GitHub15> [artiq] gkasprow commented on issue #854: How to test the packet loss rate? https://github.com/m-labs/artiq/issues/854#issuecomment-360986416
<GitHub30> [artiq] sbourdeauducq commented on issue #854: Good, though I don't know why the link is down on my board.... https://github.com/m-labs/artiq/issues/854#issuecomment-360986588
<GitHub17> [artiq] gkasprow commented on issue #854: Yes, I applied Rx clock fix, I posted pictures with short note how to implement on other boards.... https://github.com/m-labs/artiq/issues/854#issuecomment-360987204
<sb0> bb-m-labs, force build misoc
<bb-m-labs> build forced [ETA 4m44s]
<bb-m-labs> I'll give a shout when the build finishes
<GitHub137> [misoc] sbourdeauducq tagged 0.9 at master: https://github.com/m-labs/misoc/commits/0.9
<bb-m-labs> build #378 of misoc is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/misoc/builds/378
<GitHub58> [artiq] sbourdeauducq pushed 1 new commit to release-3: https://github.com/m-labs/artiq/commit/8276c6588b8b1b352175d1ed0e84697de9875abc
<GitHub58> artiq/release-3 8276c65 Sebastien Bourdeauducq: conda: use misoc release
<sb0> bb-m-labs, stop build artiq release
<bb-m-labs> build 2006 interrupted
<bb-m-labs> build #2006 of artiq is complete: Exception [exception interrupted] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2006 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<GitHub121> [artiq] sbourdeauducq tagged 3.3 at 0c2afff: https://github.com/m-labs/artiq/commits/3.3
<sb0> bb-m-labs, force build artiq
<bb-m-labs> build forced [ETA 41m20s]
<bb-m-labs> I'll give a shout when the build finishes
<sb0> bb-m-labs, stop build artiq wrong branch
<bb-m-labs> build 2007 interrupted
<bb-m-labs> build #2007 of artiq is complete: Exception [exception conda_build_output_1] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2007
<sb0> bb-m-labs, force build --branch=release-3 artiq
<bb-m-labs> build forced [ETA 41m20s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #1152 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1152
<bb-m-labs> build #2008 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2008
<sb0> ffs
<GitHub128> [artiq] sbourdeauducq deleted 3.3 at 0c2afff: https://github.com/m-labs/artiq/commit/0c2afff
<sb0> bb-m-labs, force build migen
<bb-m-labs> build forced [ETA 4m04s]
<bb-m-labs> I'll give a shout when the build finishes
<GitHub150> [migen] sbourdeauducq tagged 0.7 at master: https://github.com/m-labs/migen/commits/0.7
<bb-m-labs> build #241 of migen is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/migen/builds/241
<GitHub100> [artiq] sbourdeauducq pushed 1 new commit to release-3: https://github.com/m-labs/artiq/commit/59fe69a4b305967e4b0dbd025f0141c6207bd3fb
<GitHub100> artiq/release-3 59fe69a Sebastien Bourdeauducq: conda: use new migen
<sb0> bb-m-labs, stop build artiq release
<bb-m-labs> build 2009 interrupted
<bb-m-labs> build #2009 of artiq is complete: Exception [exception conda_build_output] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2009 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<sb0> bb-m-labs, force build --branch=release-3 artiq
<bb-m-labs> build forced [ETA 41m20s]
<bb-m-labs> I'll give a shout when the build finishes
<GitHub98> [artiq] sbourdeauducq tagged 3.3 at f806b30: https://github.com/m-labs/artiq/commits/3.3
<sb0> bb-m-labs: force build --props=package=artiq-kc705-nist_qc2 --branch=release-3 artiq-board
<bb-m-labs> The build has been queued, I'll give a shout when it starts
<GitHub145> [artiq] sbourdeauducq commented on issue #723: What kind of speed improvement can we expect from this, exactly? https://github.com/m-labs/artiq/issues/723#issuecomment-360992927
<GitHub188> [artiq] sbourdeauducq commented on issue #723: What kind of speed improvement can we expect from this, exactly? (compared to the whole ARTIQ stack) https://github.com/m-labs/artiq/issues/723#issuecomment-360992927
<bb-m-labs> build #1153 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1153
<bb-m-labs> build forced [ETA 20m15s]
<bb-m-labs> I'll give a shout when the build finishes
<GitHub3> [artiq] whitequark commented on issue #723: You can run the profiler, then cut the time spent doing anything LLVM-related in half. https://github.com/m-labs/artiq/issues/723#issuecomment-360993011
<bb-m-labs> build #2010 of artiq is complete: Failure [failed artiq_flash] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2010
<GitHub39> [artiq] whitequark pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/eed2db3a9834a65dee7d2b12c614453888205d3f
<GitHub39> artiq/master eed2db3 whitequark: artiq_flash: make the proxy action unnecessary.
<sb0> whitequark, re. the artiq_flash issue: could it be that it attempts to use one of the kasli I connected recently, thinking it is the kc705?
<sb0> openocd has very few checks against bitstream loading problems...
<whitequark> hm
<whitequark> maybe. artiq_flash on buildbot doesn't use preinit_command
<whitequark> so, which one *is* the kc705?
<sb0> since the kc705 boots, it is unlikely that the flash is damaged
<sb0> let me check ...
<sb0> 3:9
<bb-m-labs> build #1154 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1154
<sb0> or you can use ftdi_serial 210203357753
<whitequark> do kaslis not have unique serial numbers btw?
<whitequark> and saymas...
<sb0> not until someone flashes the ftdi-chips
<whitequark> ok
<sb0> and since the tools for doing that are garbage, it's more annoying than using ftdi_location
<whitequark> I'll do that as a part of my FTDI emulation board I guess
<whitequark> confirmed that it works with ftdi_serial
<sb0> how will that ftdi emulation board be connected to the existing hardware?
<sb0> okay, good. so it was a pretty simple problem.
<whitequark> it has JTAG headers, right?
<sb0> yes but not UART ones, and for sayma those boards will end up in a microTCA chassis with little space to add extra boards
<bb-m-labs> build #1155 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1155 blamelist: whitequark <whitequark@whitequark.org>
<bb-m-labs> build #2011 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2011 blamelist: whitequark <whitequark@whitequark.org>
<whitequark> ah I see. but what I meant is I'll write a Python tool for reflashing boards.
<sb0> something like this: http://www.nateurope.com/zoomimg/70.jpg
<whitequark> so you could do that to the FTDI chips that are already on them.
<sb0> mh, ftdi_location + labeled USB cables is faster
<whitequark> if you never change topology...
<sb0> bb-m-labs: force build --props=package=artiq-kc705-nist_qc2 --branch=release-3 artiq-board
<bb-m-labs> build forced [ETA 20m15s]
<bb-m-labs> I'll give a shout when the build finishes
bb-m-labs has quit [Quit: buildmaster reconfigured: bot disconnecting]
<GitHub-m-labs> [buildbot-config] whitequark pushed 1 new commit to master: https://git.io/vNMPb
<GitHub-m-labs> buildbot-config/master a00c088 whitequark: Use --preinit-command when flashing the test board.
<GitHub-m-labs> [buildbot-config] whitequark force-pushed master from a00c088 to 683d006: https://git.io/v1foL
<GitHub-m-labs> buildbot-config/master 683d006 whitequark: Use --preinit-command when flashing the test board.
<GitHub-m-labs> [buildbot-config] whitequark force-pushed master from 683d006 to e3efae2: https://git.io/v1foL
<GitHub-m-labs> buildbot-config/master e3efae2 whitequark: Use --preinit-command when flashing the test board.
bb-m-labs has joined #m-labs
<whitequark> force build --props=package=artiq-kc705-nist_qc2 --branch=release-3 artiq-board
<whitequark> bb-m-labs: force build --props=package=artiq-kc705-nist_qc2 --branch=release-3 artiq-board
<bb-m-labs> build #1157 forced
<bb-m-labs> I'll give a shout when the build finishes
<sb0> whitequark, it's retrying automatically already
<whitequark> oh
<sb0> hm, not sure
<sb0> it seems to have merged the retry and your request
<whitequark> nope, don't think so
<whitequark> oh
<whitequark> yeah it does that
<GitHub115> [artiq] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/3231d8b235bec3c8c2c8da73cfff8740f61c462a
<GitHub115> artiq/master 3231d8b Sebastien Bourdeauducq: RELEASE_NOTES: 3.3
<GitHub107> [artiq] sbourdeauducq pushed 1 new commit to release-3: https://github.com/m-labs/artiq/commit/bfb03fdbba90dcf8d415a3c694ed80733c8fc12a
<GitHub107> artiq/release-3 bfb03fd Sebastien Bourdeauducq: RELEASE_NOTES: 3.3
<bb-m-labs> build #2012 of artiq is complete: Failure [failed python_coverage] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2012 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<bb-m-labs> build #1157 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1157
<GitHub193> [artiq] sbourdeauducq commented on issue #407: @r-srinivas @dhslichter I suppose the following experiment can be used instead of a scope:... https://github.com/m-labs/artiq/issues/407#issuecomment-360997773
<GitHub107> [artiq] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/e8ed3475ea3d3fd38bc093672c56af57b3cdb5f9
<GitHub107> artiq/master e8ed347 Sebastien Bourdeauducq: test: add kernel overhead test (#407)
<GitHub189> [artiq] sbourdeauducq commented on issue #407: @r-srinivas @dhslichter I suppose the following experiment can be used instead of a scope:... https://github.com/m-labs/artiq/issues/407#issuecomment-360997773
<bb-m-labs> build #1158 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1158
<bb-m-labs> build #2013 of artiq is complete: Failure [failed artiq_flash] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2013 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<sb0> whitequark, ^
<sb0> and if you change the command-line arguments between master and release-3, we have a problem (unless the buildbot does different invokations for each branch)
<whitequark> sb0: well release-3 will just never flash successfully now, because it lacks --preinit-command too.
<bb-m-labs> build #1159 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1159
<bb-m-labs> build #2014 of artiq is complete: Failure [failed artiq_flash] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2014 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<sb0> whitequark, OpenOCD syntax error in expression: "(cat /var/lib/artiq/boards/kc705-1)"
<sb0> whitequark, can you add --preinit-command to release-3?
bb-m-labs has quit [Quit: buildmaster reconfigured: bot disconnecting]
<GitHub-m-labs> [buildbot-config] whitequark pushed 1 new commit to master: https://git.io/vNMyi
<GitHub-m-labs> buildbot-config/master a48ec0a whitequark: Use openocd TCL source command instead of shell.
bb-m-labs has joined #m-labs
<whitequark> can't you cherry-pick 4a57b52241c3e1446120d825a90e894301142a74 and add the -I variant?
<sb0> bb-m-labs, force build artiq
<bb-m-labs> build #2015 forced
<bb-m-labs> I'll give a shout when the build finishes
<GitHub156> [artiq] sbourdeauducq pushed 3 new commits to master: https://github.com/m-labs/artiq/compare/e8ed3475ea3d...0aacdb045867
<GitHub156> artiq/master 0aacdb0 Sebastien Bourdeauducq: tools: add missing import
<GitHub156> artiq/master 6f90a43 Sebastien Bourdeauducq: examples: reorganize for new hardware
<GitHub156> artiq/master 67625fe Sebastien Bourdeauducq: test: check kernel overhead credibility
<bb-m-labs> build #1160 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1160
<bb-m-labs> build #2015 of artiq is complete: Failure [failed python_coverage_1] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2015
<whitequark> sb0: why do we even build amc and rtm firmware separately?
<whitequark> gateware*
<bb-m-labs> build #1161 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1161
<bb-m-labs> build #2016 of artiq is complete: Failure [failed python_coverage_1] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2016 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<GitHub105> [artiq] whitequark pushed 2 new commits to master: https://github.com/m-labs/artiq/compare/0aacdb045867...11a8b84355d7
<GitHub105> artiq/master 11a8b84 whitequark: Merge the build trees of sayma_amc and sayma_rtm targets....
<GitHub105> artiq/master 0b9c551 whitequark: artiq_flash: implement flash read functionality.
<bb-m-labs> build #1162 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1162
<bb-m-labs> build #712 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/712
<bb-m-labs> build #2017 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2017
<GitHub11> [sinara] gkasprow pushed 1 new commit to master: https://git.io/vNDeI
<GitHub11> sinara/master efd9523 Greg: Zotino 1.1 layout finished