sb0 changed the topic of #m-labs to: https://m-labs.hk :: Logs http://irclog.whitequark.org/m-labs :: Due to spam bots, only registered users can talk. See: https://freenode.net/kb/answer/registration
<sb0> bb-m-labs: force build --branch=release-3 artiq
<bb-m-labs> build forced [ETA 1h00m45s]
<bb-m-labs> I'll give a shout when the build finishes
<sb0> bb-m-labs: force build --props=package=artiq-kc705-nist_qc2 --branch=release-3 artiq-board
<bb-m-labs> build forced [ETA 16m41s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #1927 of artiq-board is complete: Exception [exception conda_build_output] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1927
<sb0> bb-m-labs: force build --props=package=artiq-kc705-nist_qc2 --branch=release-3 artiq-board
<bb-m-labs> build forced [ETA 16m41s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #1928 of artiq-board is complete: Exception [exception conda_build_output] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1928
<bb-m-labs> build #1929 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1929
<bb-m-labs> build #2640 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2640
<sb0> bb-m-labs: force build --props=package=artiq-kc705-nist_qc2 --branch=release-3 artiq-board
<bb-m-labs> build forced [ETA 16m41s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #1930 of artiq-board is complete: Exception [exception conda_build_output] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1930
<sb0> bb-m-labs: force build --props=package=artiq-kc705-nist_qc2 artiq-board
<bb-m-labs> build forced [ETA 16m41s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #1931 of artiq-board is complete: Exception [exception conda_build_output] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1931
<sb0> bb-m-labs: force build --props=package=artiq-board,artiq_target=kc705,artiq_variant=nist_qc2 --branch=release-3 artiq-board
<bb-m-labs> build forced [ETA 16m41s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #1932 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1932
<GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1160: Maybe rename ``verbosity_args`` to e.g. ``common_args`` then? https://github.com/m-labs/artiq/issues/1160#issuecomment-431728319
<GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1180: The proposed solution (without patch) does not work because we are using the stretch mode where "The size cannot be changed by the user or programmatically". https://github.com/m-labs/artiq/issues/1180#issuecomment-431733050
<GitHub-m-labs> [artiq] sbourdeauducq pushed 1 new commit to release-3: https://github.com/m-labs/artiq/commit/5a3d12f07b0f46aebf36a813ee0dd84edc9f8f95
<GitHub-m-labs> artiq/release-3 5a3d12f Sebastien Bourdeauducq: vivado timing test
<GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1126: @jbqubit Is this still an issue? https://github.com/m-labs/artiq/issues/1126#issuecomment-431734678
<GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1114: Can we close this? https://github.com/m-labs/artiq/issues/1114#issuecomment-431734855
<GitHub-m-labs> [artiq] sbourdeauducq closed issue #983: openocd/bscan-spi-bitstreams versions https://github.com/m-labs/artiq/issues/983
rohitksingh_work has joined #m-labs
rohitksingh_wor1 has joined #m-labs
rohitksingh_wor1 has quit [Client Quit]
rohitksingh_work has quit [Ping timeout: 245 seconds]
<bb-m-labs> build #1933 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/1933
<bb-m-labs> build #2641 of artiq is complete: Failure [failed python_unittest_3] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2641 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
m4ssi has joined #m-labs
<GitHub-m-labs> [artiq] jordens commented on issue #1171: The slightly confusing wrinkle (and probably the reason it was not like this before) is the following behavior:... https://github.com/m-labs/artiq/issues/1171#issuecomment-431769202
dlrobertson has quit [Quit: WeeChat 2.2]
dlrobertson has joined #m-labs
<sb0> hartytp: the 125MHz xtal on kasli is clocking everything, not just ethernet, and should not be removed
mumptai has joined #m-labs
<GitHub-m-labs> [artiq] jordens commented on issue #1171: The slightly confusing wrinkle (and probably the reason it was not like this before) is the following behavior:... https://github.com/m-labs/artiq/issues/1171#issuecomment-431798310
m4ssi has quit [Remote host closed the connection]
<GitHub-m-labs> [artiq] jonaskeller closed issue #1114: mutate_dataset() fails to find broadcasted datasets https://github.com/m-labs/artiq/issues/1114
<GitHub-m-labs> [artiq] drewrisinger commented on issue #1160: @sbourdeauducq That would require a fair amount of refactoring, though I agree with the idea. A quick scan of the repo shows ~15 files where `verbosity_args` is used, not counting code built on top of it. https://github.com/m-labs/artiq/issues/1160#issuecomment-431897415
<GitHub-m-labs> [artiq] drewrisinger commented on issue #1160: Also, processing the `--version` flag could be abstracted to some common function, maybe something like (in `artiq.tools`):... https://github.com/m-labs/artiq/issues/1160#issuecomment-431903346
<GitHub-m-labs> [artiq] drewrisinger commented on issue #1160: Also, processing the `--version` flag could be abstracted to some common function, maybe something like (in `artiq.tools`):... https://github.com/m-labs/artiq/issues/1160#issuecomment-431903346
<GitHub-m-labs> [artiq] drewrisinger opened pull request #1181: [tools]: Add --version flag to cmd line args (master...dr-pr-version-cmd-arg) https://github.com/m-labs/artiq/pull/1181
<GitHub-m-labs> [artiq] drewrisinger opened pull request #1182: [template]: Reorder pull request template (master...dr-pr-issue-template-2) https://github.com/m-labs/artiq/pull/1182
<GitHub-m-labs> [artiq] drewrisinger commented on issue #1160: See #1181 for related PR. https://github.com/m-labs/artiq/issues/1160#issuecomment-431939942
hartytp has joined #m-labs
hartytp has quit [Client Quit]
hartytp has joined #m-labs
hartytp has quit [Client Quit]
hartytp has joined #m-labs
hartytp has quit [Client Quit]
hartytp has joined #m-labs
<hartytp> sb0: yes. I wasn't suggesting removing the XO. Just asking whether it needs to be on a MGTREF pin, or if it can be any old cc pin (assuming we can fine a spare cc pin, but that's a separate question)
<hartytp> anyway, any suggestions as to the simplest method for implementing the DDMTD PLL on Kasli are welcome
hartytp_ has joined #m-labs
<hartytp_> sb0: also, apologies it's taken me so long to test out the switching branch. we had some issues with the Kaslis that I was planning to use for testing. I'm expecting a fresh batch to arrive tomorrow. Will prioritise testing once they arrive
hartytp_ has quit [Client Quit]
hartytp has quit [Ping timeout: 256 seconds]
<rjo> hartytp: what kind of issues with kasli if i may ask?
mumptai has quit [Quit: Verlassend]
<GitHub-m-labs> [artiq] drewrisinger commented on issue #1181: Fixed commits to use `argparse`'s `--version` built-in action (`parser.add_argument("--version", action="version", version="ARTIQ v...")`) https://github.com/m-labs/artiq/pull/1181#issuecomment-432010432
futarisIRCcloud has joined #m-labs