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
fengling__ has joined #m-labs
fengling__ has quit [Ping timeout: 240 seconds]
fengling__ has joined #m-labs
sb0 has joined #m-labs
fengling__ is now known as fengling
<sb0> whitequark, I have reflashed the kc705 with 1.1 and it pings again...
<whitequark> yes
<whitequark> have you read the log above
<whitequark> there's a certain commit. the build before it works, any builds after it don't
<whitequark> by "the build before it" I mean any builds built on CI and uploaded to anaconda before that commit
<sb0> yes, I have read the log, but I wanted to check that the failure was caused by a change in the code and not some hardware issue that popped up
<whitequark> sure
<whitequark> I've tested the changes yesterday using 1.1
<whitequark> actually, no, using the bitstream from http://buildbot.m-labs.hk/builders/artiq/builds/784
<sb0> bb-m-labs, force build --revision=dd349b0701cc4168ebb5fa58e0dfd2e8508d755a artiq
<bb-m-labs> build forced [ETA 20m20s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #519 of artiq-kc705-nist_clock is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-kc705-nist_clock/builds/519
mumptai has quit [Ping timeout: 253 seconds]
<bb-m-labs> build #246 of artiq-win64-test is complete: Failure [failed python_unittest] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/246
<bb-m-labs> build #790 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/790
<whitequark> sb0: so it's completely deterministic
<whitequark> but I don't understand why reverting the next commit doesn't work...
mumptai has joined #m-labs
<sb0> no, it's not
<sb0> that commit worked before
<sb0> er
<sb0> that's a different failure
<sb0> some windows breakage...
<sb0> maybe since the python upgrade to 3.5.2?
<sb0> bb-m-labs, force build --revision=4a6c270afe8e65f611d69ec5004cfca81a224672 artiq
<bb-m-labs> build forced [ETA 20m20s]
<bb-m-labs> I'll give a shout when the build finishes
<sb0> did python fuck up asyncio.open_connection on windows in 3.5.2? that's going to be fun
<sb0> sigh
<whitequark> sb0: I got your optics
<sb0> cool, thanks
<bb-m-labs> build #520 of artiq-kc705-nist_clock is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-kc705-nist_clock/builds/520
<bb-m-labs> build #247 of artiq-win64-test is complete: Failure [failed python_unittest] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/247
<bb-m-labs> build #791 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/791
<sb0> bb-m-labs, force build --revision=71921de5bde602b7e65f4a79dffda6a60f3ffe84 artiq
<bb-m-labs> build forced [ETA 20m20s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #521 of artiq-kc705-nist_clock is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-kc705-nist_clock/builds/521
<bb-m-labs> build #792 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/792
<sb0> vivado garbage
<sb0> the vivado we have is pretty old, maybe they fixed that since then
<cr1901_modern> At the very least, their installation process has gotten far less fucked up, last I heard
<cr1901_modern> (Though maybe fixing two bugs is giving them too much credit :P)
<sb0> can you install in command line now or do you still need X?
<cr1901_modern> Oh, AFAIK you still need X. The bug I was referring to is that the installer was hardcoded to check a specific interface to generate your product ID, and if you don't have an "eth0" you couldn't install it
<sb0> my preferred way of deploying xilinx tools is to install it once, tarball it, decompress on every machine that needs it and use udev to set the MAC address to whatever their licensing shitware wants
<cr1901_modern> Doesn't cause problems on your network that two devices have same MAC address?
<sb0> yes. many systems don't have a eth0, and since you need udev to create one, you might as well take care of the MAC as well
<sb0> yes, that doesn't work if you connect two of those tweaked interfaces to the same net
<sb0> you can also give it virtual tun/tap interface
<cr1901_modern> I don't understand how that solves the problem (b/c I don't actually know what a tun/tap interface does :P)
<cr1901_modern> I haven't actually installed Vivado yet b/c I need to nuke my Linux install and extend my Windoze partition. Only problem is that GRUB is right after my Windows partition and I'm unsure how to move it without have access to grubinst
<cr1901_modern> grub-install*
<GitHub85> [artiq] sbourdeauducq pushed 3 new commits to master: https://git.io/vKqZc
<GitHub85> artiq/master 520b269 Sebastien Bourdeauducq: RELEASE_NOTES: artiq_client persist flag
<GitHub85> artiq/master ea10a2a Sebastien Bourdeauducq: manual/faq: update for inter-experiment seamless handover
<GitHub85> artiq/master d2d897a Sebastien Bourdeauducq: manual/getting_started: add examples location info, closes #501
<sb0> well, I guess the problem is open_connection() will now raise OSError instead of ConnectionRefusedError when attempting to connect to a closed port on localhost
<whitequark> sb0: I need the kc705 now
<whitequark> going to use it for a few minutes
<sb0> okay, you can stop that build
<sb0> bb-m-labs, stop build artiq
<bb-m-labs> try 'stop build WHICH <REASON>'
<sb0> bb-m-labs, stop build artiq kc705
<bb-m-labs> build 793 interrupted
<bb-m-labs> build #522 of artiq-kc705-nist_clock is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-kc705-nist_clock/builds/522
<bb-m-labs> build #793 of artiq is complete: Exception [exception] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/793 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
FabM has joined #m-labs
<GitHub129> [artiq] sbourdeauducq pushed 1 new commit to release-1: https://git.io/vKqcA
<GitHub129> artiq/release-1 d96d222 Sebastien Bourdeauducq: targets/kc705: fix import
<whitequark> wtf
<whitequark> why cannot you compare numpy arrays?
<whitequark> (numpy.array([42, 43]),) == (numpy.array([42, 43]),)
<whitequark> ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()
<whitequark> oh, it tries to do element-by-element comparison
<sb0> bb-m-labs, force build artiq-kc705-nist_qc2
<bb-m-labs> build #172 forced
<bb-m-labs> I'll give a shout when the build finishes
<sb0> there are probably some conda cache problems going on again. https://github.com/m-labs/artiq/issues/502 is reproducible outside the automatic build
<sb0> and what causes it is migen commit 5630b7c81422184de272d49e0c9d9c29240278dd from June 11
<sb0> hmm, does it take main or dev for installing migen?
<sb0> and the SMA voltage situation is: the default is 2.5V indeed, but since NIST are connecting 3.3V DDSes directly on the same I/O bank and K7 FPGAs cannot take input voltages higher than VCCO (something that was found only after the boards were made, of course) the KC705 power controller is reprogrammed to set those to 3.3
<bb-m-labs> build #172 of artiq-kc705-nist_qc2 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-kc705-nist_qc2/builds/172
<GitHub56> [artiq] whitequark pushed 2 new commits to master: https://git.io/vKq83
<GitHub56> artiq/master d90fd7d whitequark: compiler: implement numpy.full (#424).
<GitHub56> artiq/master 7a671fb whitequark: embedding: treat numpy.{int32,int64,array} specially (#424)....
<sb0> whitequark, done with the kc705?
<bb-m-labs> build #523 of artiq-kc705-nist_clock is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-kc705-nist_clock/builds/523
<bb-m-labs> build #794 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/794 blamelist: whitequark <whitequark@whitequark.org>
<GitHub34> [artiq] sbourdeauducq pushed 2 new commits to master: https://git.io/vKqBt
<GitHub34> artiq/master c065b58 Sebastien Bourdeauducq: require Python 3.5.2, remove monkey patches
<GitHub34> artiq/master 8cb29fc Sebastien Bourdeauducq: targets/kc705: redefine user SMAs as 3.3V IO. Closes #502
<GitHub153> [artiq] sbourdeauducq pushed 1 new commit to release-1: https://git.io/vKqBO
<GitHub153> artiq/release-1 adcf53f Sebastien Bourdeauducq: targets/kc705: redefine user SMAs as 3.3V IO. Closes #502
<sb0> whitequark, if migen builds are going to trigger misoc and artiq builds, the latter should use the migen package just built ...
<bb-m-labs> build #524 of artiq-kc705-nist_clock is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-kc705-nist_clock/builds/524
<bb-m-labs> build #795 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/795 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<sb0> I'm downloading the new vivado, will try to upgrade the buildserver
<sb0> of course...
<whitequark> sb0: I think that should work
<whitequark> uh
<whitequark> I hope our vivado isn't exposed to the internet
<sb0> it obviously doesn't: before those commits I had pushed, building from migen master results in the issue Raghu has reported, whereas the automatic build succeeds (see above)
<sb0> we're using the node-locked license, fortunately, so it doesn't open ports
fengling has quit [Ping timeout: 240 seconds]
fengling has joined #m-labs
<whitequark> hey sb0 I just had an idea for a ghetto instrument
<whitequark> take any cheap LA
<whitequark> like those $15 chinese clones of saleae
<whitequark> put a voltage to frequency converter on every input, which you can possibly bypass
<whitequark> this allows you to capture analog channels synchronized with digital channels, on an arbitrary set of inputs, and with a natural choice between resolution and sample rate
<GitHub24> [artiq] whitequark pushed 1 new commit to master: https://git.io/vKq2i
<GitHub24> artiq/master 373578b whitequark: embedding: fix location for diagnostics on quoted values....
mumptai has quit [Remote host closed the connection]
sb0 has quit [Ping timeout: 246 seconds]
<bb-m-labs> build #796 of artiq is complete: Failure [failed lit_test] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/796 blamelist: whitequark <whitequark@whitequark.org>
fengling has quit [Ping timeout: 240 seconds]
sb0 has joined #m-labs
fengling has joined #m-labs
sb0 has quit [Ping timeout: 260 seconds]
sb0 has joined #m-labs
<GitHub103> [artiq] sbourdeauducq pushed 1 new commit to release-1: https://git.io/vKqrr
<GitHub103> artiq/release-1 a801cde whitequark: embedding: fix location for diagnostics on quoted values....
<whitequark> uhm, that failed tests
<whitequark> I was about to push the fix
<sb0> ok, please push it to release-1 as well
sb0 has quit [Ping timeout: 258 seconds]
rohitksingh has joined #m-labs
sb0 has joined #m-labs
sb0 has quit [Read error: Connection reset by peer]
sb0 has joined #m-labs
sb0 has quit [Ping timeout: 246 seconds]
sb0 has joined #m-labs
fengling has quit [Ping timeout: 240 seconds]
<sb0> cr1901_modern, the installer did *not* improve
<sb0> I can't even run it
<sb0> ERROR: This installation is not supported on 32 bit platforms.
<sb0> even though it is running on 64
fengling has joined #m-labs
<whitequark> yes
<whitequark> unpack it manually and fix the uname
<whitequark> change uname -i to uname -m in the xsetup.sh script, to be specififc
fengling has quit [Ping timeout: 240 seconds]
<GitHub189> [pythonparser] whitequark pushed 2 new commits to master: https://git.io/vKqFT
<GitHub189> pythonparser/master 5cb107b whitequark: diagnostic.Engine: allow adding contextual notes.
<GitHub189> pythonparser/master 03d87cb whitequark: Fix python default argument idiocy.
<GitHub189> [pythonparser] whitequark pushed 1 new commit to master: https://git.io/vKqFN
<GitHub189> pythonparser/master c744600 whitequark: diagnostic.Engine: allow adding multiple notes at once.
<GitHub65> [artiq] whitequark pushed 1 new commit to master: https://git.io/vKqNf
<GitHub65> artiq/master 5a79fcf whitequark: embedding: reimplement 373578bc properly....
<whitequark> bb-m-labs: force build --props=package=pythonparser conda-linux64
<bb-m-labs> no such builder 'conda-linux64'
<whitequark> bb-m-labs: force build --props=package=pythonparser conda-lin64
<bb-m-labs> build #163 forced
<bb-m-labs> I'll give a shout when the build finishes
<GitHub32> [conda-recipes] whitequark pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/aa093cc881cd6b996602c2d8fd933d71c69b4ebf
<GitHub32> conda-recipes/master aa093cc whitequark: pythonparser: bump.
<bb-m-labs> build #163 of conda-lin64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/163
<bb-m-labs> build #797 of artiq is complete: Failure [failed lit_test] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/797 blamelist: whitequark <whitequark@whitequark.org>
<whitequark> bb-m-labs: force build artiq
<bb-m-labs> build forced [ETA 20m20s]
<bb-m-labs> I'll give a shout when the build finishes
rohitksingh has quit [Ping timeout: 246 seconds]
<bb-m-labs> build #525 of artiq-kc705-nist_clock is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-kc705-nist_clock/builds/525
<bb-m-labs> build #798 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/798
fengling has joined #m-labs
flaviusb has quit [Ping timeout: 250 seconds]
<GitHub34> [artiq] whitequark pushed 1 new commit to master: https://git.io/vKmeO
<GitHub34> artiq/master 653eeb4 whitequark: runtime: fix serialization of object lists....
<bb-m-labs> build #799 of artiq is complete: Exception [exception interrupted] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/799 blamelist: whitequark <whitequark@whitequark.org>
fengling has quit [Ping timeout: 240 seconds]
fengling has joined #m-labs
sb0 has quit [Read error: Connection reset by peer]
sb0 has joined #m-labs
fengling has quit [Ping timeout: 240 seconds]
<sb0> whitequark, can you cherry-pick the other one? there are conflicts.
<GitHub102> [artiq] sbourdeauducq pushed 1 new commit to release-1: https://git.io/vKm83
<GitHub102> artiq/release-1 6a1706b whitequark: runtime: fix serialization of object lists....
fengling has joined #m-labs
fengling has quit [Ping timeout: 240 seconds]
<GitHub33> [conda-recipes] whitequark pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/5803bd9b729fea336184c423751bc3f2e6e99555
<GitHub33> conda-recipes/master 5803bd9 whitequark: libgit2: build as Release....
rohitksingh has joined #m-labs
<whitequark> bb-m-labs: force build --props=package=libgit2 conda-all
<bb-m-labs> build #61 forced
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #164 of conda-lin64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/164
<bb-m-labs> build #145 of conda-win32 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-win32/builds/145
<bb-m-labs> build #136 of conda-win64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-win64/builds/136
<bb-m-labs> build #61 of conda-all is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-all/builds/61
<sb0> the xilinx installer also cannot start into a Xvnc server
<sb0> there's some java x11 garbage that crashes immediately
<whitequark> no
<whitequark> that's not java
<whitequark> Xvnc is complete trash
<whitequark> most likely what happens is it uses 8-bit color mode, which almost nothing supports these days
<whitequark> Xvnc is broken from both the X side and the VNC side, practically speaking. amazingly useless piece of software
<sb0> sure. and if X worked correctly, we would not need Xvnc
<whitequark> try -depth 24
<whitequark> for Xvnc
<sb0> nope
<sb0> hm, actually it starts, if I don't use sudo
<sb0> installing ...
<GitHub85> [conda-recipes] whitequark pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/abe4f533aa6cf942a2567a3f2b4376cb8e600225
<GitHub85> conda-recipes/master abe4f53 whitequark: libssh2: build as Release....
<whitequark> bb-m-labs: force build --props=package=libssh2 conda-all
<bb-m-labs> build forced [ETA 4m40s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #165 of conda-lin64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/165
<bb-m-labs> build #146 of conda-win32 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-win32/builds/146
<bb-m-labs> build #137 of conda-win64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-win64/builds/137
<bb-m-labs> build #62 of conda-all is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-all/builds/62
<whitequark> *facedesk*
<whitequark> -DCMAKE_BUILD_TYPE doesn't do anything when building on msvc
<whitequark> bb-m-labs: force build --props=package=libssh2 conda-all
<bb-m-labs> build forced [ETA 3m28s]
<bb-m-labs> I'll give a shout when the build finishes
<whitequark> bb-m-labs: force build --props=package=libgit2 conda-all
<bb-m-labs> build forced [ETA 3m28s]
<bb-m-labs> I'll give a shout when the build finishes
<GitHub111> [conda-recipes] whitequark pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/1b5c7674fc3e1b054fa9784f79dd153b2b847cfc
<GitHub111> conda-recipes/master 1b5c767 whitequark: libgit2, libssh2: actually build as Release on MSVC.
<bb-m-labs> build #166 of conda-lin64 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/166
<bb-m-labs> build #147 of conda-win32 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-win32/builds/147
<bb-m-labs> build #138 of conda-win64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-win64/builds/138
<bb-m-labs> build #63 of conda-all is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/conda-all/builds/63
<sb0> bb-m-labs, force build artiq
<bb-m-labs> build forced [ETA 20m20s]
<bb-m-labs> I'll give a shout when the build finishes
<whitequark> bb-m-labs: force build --props=package=libssh2 conda-all
<bb-m-labs> The build has been queued, I'll give a shout when it starts
<GitHub25> [conda-recipes] whitequark pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/12ccd3b0f56501819692d253f970bd87258718a7
<GitHub25> conda-recipes/master 12ccd3b whitequark: libssh2: fix screwup.
<bb-m-labs> build #167 of conda-lin64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/167
<bb-m-labs> build #148 of conda-win32 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-win32/builds/148
<bb-m-labs> build #139 of conda-win64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-win64/builds/139
<bb-m-labs> build #64 of conda-all is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-all/builds/64
<bb-m-labs> build forced [ETA 4m54s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #149 of conda-win32 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-win32/builds/149
<bb-m-labs> build #140 of conda-win64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-win64/builds/140
<bb-m-labs> build #168 of conda-lin64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/168
<bb-m-labs> build #65 of conda-all is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-all/builds/65
sb0 has quit [Quit: Leaving]
<bb-m-labs> build #526 of artiq-kc705-nist_clock is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-kc705-nist_clock/builds/526
<bb-m-labs> build #800 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/800
fengling has joined #m-labs
fengling has quit [Ping timeout: 240 seconds]
<GitHub52> [artiq] whitequark pushed 1 new commit to release-1: https://git.io/vKmKP
<GitHub52> artiq/release-1 2678bb0 whitequark: embedding: reimplement 373578bc properly....
rohitksingh has quit [Ping timeout: 264 seconds]
rohitksingh has joined #m-labs
rohitksingh has quit [Ping timeout: 272 seconds]
mumptai has joined #m-labs
rohitksingh has joined #m-labs
rohitksingh has quit [Ping timeout: 272 seconds]
fengling has joined #m-labs
fengling has quit [Ping timeout: 240 seconds]
FabM has quit [Quit: ChatZilla 0.9.92 [Firefox 47.0/20160604131506]]
rohitksingh has joined #m-labs
fengling has joined #m-labs
fengling has quit [Ping timeout: 240 seconds]
rohitksingh has quit [Quit: Leaving.]
fengling has joined #m-labs
sandeepkr has quit [Quit: Leaving]
fengling has quit [Ping timeout: 240 seconds]
sandeepkr has joined #m-labs
fengling has joined #m-labs
fengling has quit [Ping timeout: 240 seconds]
mumptai has quit [Quit: Verlassend]
fengling has joined #m-labs
fengling has quit [Ping timeout: 240 seconds]
<GitHub69> [artiq] jordens pushed 2 new commits to master: https://git.io/vKY7z
<GitHub69> artiq/master 2a5a1f3 Robert Jordens: browser, worker: feed experiments dummy devices, closes #454...
<GitHub69> artiq/master b7cca38 Robert Jordens: browser: let the state manager handle the subcomponents
<bb-m-labs> build #527 of artiq-kc705-nist_clock is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-kc705-nist_clock/builds/527 blamelist: Robert Jordens <rj@m-labs.hk>
<bb-m-labs> build #801 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/801 blamelist: Robert Jordens <rj@m-labs.hk>