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
gric has joined #m-labs
evilspirit has joined #m-labs
fengling has joined #m-labs
fengling has quit [Quit: WeeChat 1.4]
evilspirit has quit [Ping timeout: 240 seconds]
fengling has joined #m-labs
fengling has quit [Quit: WeeChat 1.4]
fengling has joined #m-labs
evilspirit has joined #m-labs
<whitequark> sb0: no, you're confused about the role of qemu
<whitequark> qemu provides a device model here
<whitequark> whereas xen provides virtualized code execution
<whitequark> since compiling is a CPU-bound task, this pays off
<whitequark> if we had a disk-bound task, there would be little difference, for example
<whitequark> as for connecting to X, I don't think you can do that with xen, no; the qemu device model binary doesn't have any X in it
<whitequark> rjo: ok. yes. I see.
<whitequark> we need another build machine, this time it will be an ubuntu-trusty64. it will run the conda-lin64 buildbot.
kyak_ is now known as kyak
fengling has quit [Ping timeout: 240 seconds]
fengling has joined #m-labs
<sb0> qemu-system-i386 *is* loading X and SDL libs. and I do remember using qemu-system-lm32 that popped out a X11 windows.
<whitequark> hm, hang on, I have a better idea
<whitequark> why don't you install tightvncserver *on the windows machine*?
<sb0> that would solve the current bugs, but also I'm still trying to understand why you wrote a vnc client
<whitequark> as far as I'm aware you can't use sdl or x from under xen
<sb0> (and assuming, of course, that tightvncserver isn't another clusterfuck like the cygwin sshd)
<sb0> why do we need two build machines?
<whitequark> because host's glibc is too new
<whitequark> well, three
<whitequark> I don't mean a physical machine, we just need a trusty64 VM
<sb0> ok. and probably more RAM as well
<whitequark> more RAM never hurts
<sb0> right now there are two windows VMs running and that would make three VMs, plus it needs to run ISE, right?
<whitequark> two ISE copies at once, right now
<sb0> isn't it swapping?
<whitequark> pretty sure it does
<whitequark> note that VMs cannot be swapped out, I think
<whitequark> at least Xen refuses to allocate a VM with more RAM than physical
<whitequark> oh
<whitequark> yeah, right, the idea is that VMs should do their own swap management
<whitequark> since Xen's would be inefficient
<whitequark> this is much less of a problem with Linux VMs since they can use balloon (dynamically request RAM from Xen)
<sb0> http://xenbits.xen.org/docs/4.2-testing/man/xl.cfg.5.html seems to suggest SDL and even OpenGL work with Xen
<sb0> anyway, more RAM is cheap and in theory easy
<whitequark> there can be up to 16GB of RAM on this motherboard
<whitequark> that's the first time I hear about SDL. yeah, I guess a VNC client wasn't necessary then.
<whitequark> hm, so right now buildserver has 8GB of RAM
<whitequark> around 3GB is for dom0, the rest is allocated to VMs
<whitequark> so we at least have room for an ubuntu64 vm
<sb0> would have been surprising if there was no reliable graphical display out of VMs. that's one of the essential features of a widely used program
<sb0> cr1901_modern, zooming is much better, but still a bit fof
<sb0> *off
<sb0> cr1901_modern, I think you really send mouse wheel events from the sliders into the axis (or otherwise make the slider area also zoom reactive)
<sb0> cr1901_modern, when I zoom in a lot between the cursors, the cursors do not disappear (as they become out of range) - they should. but i guess you are already planning to implement that?
<sb0> better if they disappear progressively, i.e. the cursor can be straddling the widget borders. that will be needed for nice scrolling too.
sb0_ has joined #m-labs
sb0 has quit [Ping timeout: 248 seconds]
fengling has quit [Ping timeout: 240 seconds]
<whitequark> the webkit people are insane
fengling has joined #m-labs
<larsc> what did they do now?
<whitequark> you need python, ruby and perl to build qtwebkit
<whitequark> ok
<whitequark> seems like i have a decent qt package
<whitequark> now to make it work.
<whitequark> bb-m-labs: force build --props=package=qt5 conda-win64
<bb-m-labs> build forced [ETA 37m18s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #42 of conda-win64 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-win64/builds/42
<whitequark> good start
<whitequark> oh
<whitequark> bb-m-labs: force build --props=package=qt5 conda-win64
<bb-m-labs> build forced [ETA 37m18s]
<bb-m-labs> I'll give a shout when the build finishes
<GitHub38> [conda-recipes] whitequark pushed 2 new commits to master: https://github.com/m-labs/conda-recipes/compare/dbafcfecae0f...641aa592ada0
<GitHub38> conda-recipes/master 18fdd3b whitequark: qt: remove.
<GitHub38> conda-recipes/master 641aa59 whitequark: qt5: add.
rohitksingh has joined #m-labs
<whitequark> bb-m-labs: force build --props=package=qt5 conda-lin64
<bb-m-labs> build forced [ETA 43 seconds]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #43 of conda-win64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-win64/builds/43
<bb-m-labs> build #66 of conda-lin64 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/66
<whitequark> ugh
<whitequark> wtf
<whitequark> who writes batch files like that
<whitequark> aaaargh
<whitequark> guess what, it didn't actually build on windows
<GitHub140> [conda-recipes] whitequark force-pushed master from 641aa59 to 80281d4: https://github.com/m-labs/conda-recipes/commits/master
<GitHub140> conda-recipes/master 80281d4 whitequark: qt5: add.
<whitequark> because it didn't do if errorlevel == 1 exit 1
<whitequark> (the equivalent of set -e)
<whitequark> ugh
<whitequark> cretins
<whitequark> bb-m-labs: force build --props=package=qt5 conda-lin64
<bb-m-labs> build forced [ETA 43 seconds]
<bb-m-labs> I'll give a shout when the build finishes
<whitequark> bb-m-labs: force build --props=package=qt5 conda-win64
<bb-m-labs> build forced [ETA 26m30s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #67 of conda-lin64 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/67
<whitequark> bb-m-labs: force build --props=package=qt5 conda-lin64
<bb-m-labs> build forced [ETA 43 seconds]
<bb-m-labs> I'll give a shout when the build finishes
<GitHub115> [conda-recipes] whitequark force-pushed master from 80281d4 to fd7e145: https://github.com/m-labs/conda-recipes/commits/master
<GitHub115> conda-recipes/master fd7e145 whitequark: qt5: add.
<bb-m-labs> build #68 of conda-lin64 is complete: Exception [exception interrupted] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/68
<whitequark> hm
<whitequark> bb-m-labs: force build --props=package=qt5 conda-lin64
<bb-m-labs> build forced [ETA 43 seconds]
<bb-m-labs> I'll give a shout when the build finishes
<GitHub19> [conda-recipes] whitequark force-pushed master from fd7e145 to 490f90c: https://github.com/m-labs/conda-recipes/commits/master
<GitHub19> conda-recipes/master 490f90c whitequark: qt5: add.
<bb-m-labs> build #69 of conda-lin64 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/69
<whitequark> bb-m-labs: force build --props=package=qt5 conda-lin64
<bb-m-labs> build forced [ETA 43 seconds]
<bb-m-labs> I'll give a shout when the build finishes
<GitHub97> [conda-recipes] whitequark force-pushed master from 490f90c to 2a9ff56: https://github.com/m-labs/conda-recipes/commits/master
<GitHub97> conda-recipes/master 2a9ff56 whitequark: qt5: add.
<bb-m-labs> build #70 of conda-lin64 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/70
<bb-m-labs> build #44 of conda-win64 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-win64/builds/44
<whitequark> bb-m-labs: force build --props=package=qt5 conda-lin64
<bb-m-labs> build forced [ETA 43 seconds]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #71 of conda-lin64 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/71
fengling has quit [Quit: WeeChat 1.4]
<GitHub85> [conda-recipes] whitequark force-pushed master from 2a9ff56 to 33043ca: https://github.com/m-labs/conda-recipes/commits/master
<GitHub85> conda-recipes/master 33043ca whitequark: qt5: add.
<whitequark> bb-m-labs: force build --props=package=qt5 conda-lin64
<bb-m-labs> build forced [ETA 43 seconds]
<bb-m-labs> I'll give a shout when the build finishes
<whitequark> bb-m-labs: force build --props=package=qt5 conda-win64
<bb-m-labs> build forced [ETA 26m30s]
<bb-m-labs> I'll give a shout when the build finishes
<GitHub175> [conda-recipes] whitequark force-pushed master from 33043ca to 2430243: https://github.com/m-labs/conda-recipes/commits/master
<GitHub175> conda-recipes/master 2430243 whitequark: qt5: add.
<bb-m-labs> build #72 of conda-lin64 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/72
<whitequark> hm, now it can't find ICU
<whitequark> but I gave it ICU
<whitequark> /var/lib/buildbot/slaves/debian-stretch-amd64-1/miniconda/envs/_build/lib
<whitequark> er
<whitequark> g++ -Wl,--gc-sections -Wl,-O1 -Wl,-rpath,/var/lib/buildbot/slaves/debian-stretch-amd64-1/miniconda/envs/_build/lib/qt5 -o ../../../bin/qlalr .obj/compress.o .obj/cppgenerator.o .obj/dotgraph.o .obj/lalr.o .obj/main.o .obj/parsetable.o .obj/recognizer.o .obj/grammar.o -L/var/lib/buildbot/slaves/debian-stretch-amd64-1/miniconda/envs/_build/lib -L/var/lib/buildbot/slaves/debian-stretch-amd64-1/miniconda/conda-bld/work/qt-everywhere-opensource-src-
<whitequark> /usr/bin/ld: warning: libicui18n.so.56, needed by /var/lib/buildbot/slaves/debian-stretch-amd64-1/miniconda/conda-bld/work/qt-everywhere-opensource-src-5.5.1/qtbase/lib/libQt5Core.so, not found (try using -rpath or -rpath-link)
<whitequark> $ ls $(pwd)/libicui18n.so.56/var/lib/buildbot/slaves/debian-stretch-amd64-1/miniconda/envs/_build/lib/libicui18n.so.56
<whitequark> what the hell is your problem exactly, gcc
<sb0_> can you ldd that $(pwd)/libicui18n.so.56/var/lib/buildbot/slaves/debian-stretch-amd64-1/miniconda/envs/_build/lib/libicui18n.so.56 ?
<sb0_> not ls it
<whitequark> it's fine of course
<whitequark> what the fuck
<whitequark> it tries all the system paths and then /var/lib/buildbot/slaves/debian-stretch-amd64-1/miniconda/envs/_build/lib/qt5/libicuuc.so.56
<whitequark> and completely ignores -L/var/lib/buildbot/slaves/debian-stretch-amd64-1/miniconda/envs/_build/lib
<sb0_> .so? isn't gcc looking for .a?
<whitequark> why would it look for .a?
<whitequark> it's a dependency of Qt5Core
<whitequark> oh
<whitequark> OH that's why
<whitequark> .... hm.
<whitequark> right, it's not really designed to look outside of the prefix libdir
<whitequark> and the prefix libdir is lib/qt5.
<whitequark> that... makes a certain amount of sense
<whitequark> there was some obscure linker flag.
<whitequark> yeah, I could just add a second rpath, why the hell not
<bb-m-labs> build #45 of conda-win64 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-win64/builds/45
<whitequark> there's even an option for that in qt's configure, cool
<GitHub187> [conda-recipes] whitequark force-pushed master from 2430243 to 36f6aad: https://github.com/m-labs/conda-recipes/commits/master
<GitHub187> conda-recipes/master 36f6aad whitequark: qt5: add.
<whitequark> bb-m-labs: force build --props=package=qt5 conda-lin64
<bb-m-labs> build forced [ETA 43 seconds]
<bb-m-labs> I'll give a shout when the build finishes
<whitequark> hm, cannot find system freetype on windows
<whitequark> ah, another problem in the original recipe
<whitequark> I should've just rm'd it instead of taking it as a base.
<GitHub42> [conda-recipes] whitequark force-pushed master from 36f6aad to af4a924: https://github.com/m-labs/conda-recipes/commits/master
<GitHub42> conda-recipes/master af4a924 whitequark: qt5: add.
<whitequark> bb-m-labs: force build --props=package=qt5 conda-win64
<bb-m-labs> build forced [ETA 26m30s]
<bb-m-labs> I'll give a shout when the build finishes
<sb0_> original recipe == the spyder qt5?
<whitequark> yes
<whitequark> and it's also in conda-recipes/
<whitequark> on github
<sb0_> well they're not actually using it...
<whitequark> it's phenomenally crappy
<whitequark> yes, that explains why
acathla` has joined #m-labs
acathla has quit [Read error: Connection reset by peer]
acathla` is now known as acathla
acathla has joined #m-labs
acathla has quit [Changing host]
<whitequark> hahahahaha wow
<whitequark> I knew NTFS is bad
<whitequark> but our Windows VM spends TWENTY SIX MINUTES deleting old Qt and unpacking new
<whitequark> Qt has... 153 thousand files
<whitequark> and NTFS is really bad with lots of small files.
acathla` has joined #m-labs
acathla has quit [Read error: Connection reset by peer]
acathla` is now known as acathla
acathla has quit [Changing host]
acathla has joined #m-labs
<bb-m-labs> build #73 of conda-lin64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/73
<whitequark> it worked. amaze. wow.
<whitequark> sb0_: can you test the qt package?
<whitequark> well, it's called "qt5" again
<whitequark> oh, no pyqt...
<sb0_> whitequark, yes. can you update the artiq package and test it on linux + windows?
<whitequark> no, I can not.
<whitequark> I don't have a working conda install anywhere I have X.
<sb0_> then that's a good opportunity to verify that the full installation instructions in the manual still work
<whitequark> what do you mean?
<whitequark> if I do the full installation, I'll just use the debian qt5 package
<sb0_> that when you take a fresh anaconda or miniconda, and input the exact command in the manual, you get a working artiq.
<sb0_> someone needs to test this
<whitequark> no, you don't understand
<whitequark> conda doesn't work on my system *at all*
<rjo> whitequark: a trusty chroot would be fine.
<whitequark> ugh
<sb0_> whitequark, conda works on my system, i can reinstall it and try out the artiq install...
<whitequark> sb0_: not yet, since pyqt is not built yet
<whitequark> let me fix it up
<GitHub15> [conda-recipes] whitequark pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/0530c3b8fcd12e12a6649330818f9ed414b17630
<GitHub15> conda-recipes/master 0530c3b whitequark: pyqt: rename to pyqt5 again.
<whitequark> bb-m-labs: force build --props=package=pyqt5 conda-lin64
<bb-m-labs> build forced [ETA 20m13s]
<bb-m-labs> I'll give a shout when the build finishes
<whitequark> sb0_: does anaconda ship quamash too?
<whitequark> hm
<whitequark> should we name it quamash5?..
<bb-m-labs> build #74 of conda-lin64 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/74
<sb0_> isn't quamash qt version agnostic (and noarch)?
<whitequark> it has a dep on qt>=5
<whitequark> pyqt>=5 even
<sb0_> can the conda dependency system express pyqt | pyqt5?
<whitequark> no clue
<whitequark> bb-m-labs: force build --props=package=pyqt5 conda-lin64
<bb-m-labs> build forced [ETA 20m13s]
<bb-m-labs> I'll give a shout when the build finishes
<GitHub64> [conda-recipes] whitequark pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/3701dcaf3de84fdf69265f1f9c078b4906960a47
<GitHub64> conda-recipes/master 3701dca whitequark: pyqt5: use prefixed qmake.
<bb-m-labs> build #75 of conda-lin64 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/75
<sb0_> another solution is to remove the pyqt dependency from quamash...
<whitequark> that's stupid
<sb0_> whitequark, I see no trace of quamash in anaconda, except ours
<whitequark> what does it fucking mean "qt5-qmake is not an executable"
<bb-m-labs> build #46 of conda-win64 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-win64/builds/46
<whitequark> oh
<whitequark> bb-m-labs: force build --props=package=pyqt5 conda-lin64
<bb-m-labs> build forced [ETA 20m13s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #76 of conda-lin64 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/76
<GitHub166> [conda-recipes] whitequark force-pushed master from 3701dca to a94086f: https://github.com/m-labs/conda-recipes/commits/master
<GitHub166> conda-recipes/master a94086f whitequark: pyqt5: use prefixed qmake.
<whitequark> hm, why did the Windows build fail now...
<whitequark> qbasicfontdatabase.obj : error LNK2019: unresolved external symbol FT_New_Face referenced in function "public: static class QStringList __cdecl QBasicFontDatabase::addTTFile(class QByteArray const &,class QByteArray const &)" (?addTTFile@QBasicFontDatabase@@SA?AVQStringList@@AEBVQByteArray@@0@Z)
<whitequark> hrm
<whitequark> curious
<whitequark> bb-m-labs: force build --props=package=pyqt5 conda-lin64
<bb-m-labs> build forced [ETA 20m13s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #77 of conda-lin64 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/77
<whitequark> what the fuck
<whitequark> bb-m-labs: force build --props=package=pyqt5 conda-win64
<bb-m-labs> build forced [ETA 26m30s]
<bb-m-labs> I'll give a shout when the build finishes
<GitHub185> [conda-recipes] whitequark force-pushed master from a94086f to ff91807: https://github.com/m-labs/conda-recipes/commits/master
<GitHub185> conda-recipes/master cb0fa81 whitequark: qt5: add.
<GitHub185> conda-recipes/master b565193 whitequark: pyqt: rename to pyqt5 again.
<GitHub185> conda-recipes/master ff91807 whitequark: pyqt5: use prefixed qmake.
<bb-m-labs> build #47 of conda-win64 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-win64/builds/47
<whitequark> bb-m-labs: force build --props=package=qt5 conda-win64
<bb-m-labs> build forced [ETA 26m30s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #48 of conda-win64 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-win64/builds/48
<GitHub70> [misoc] enjoy-digital pushed 1 new commit to master: https://git.io/v2fnE
<GitHub70> misoc/master 0e44624 Florent Kermarrec: tools/flterm.py: first cleanup pass
<bb-m-labs> build #257 of artiq is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/257
evilspirit has quit [Ping timeout: 244 seconds]
evilspirit has joined #m-labs
evilspirit has quit [Ping timeout: 250 seconds]
ylamarre has joined #m-labs
<GitHub174> [artiq] sbourdeauducq pushed 1 new commit to master: https://git.io/v2flc
<GitHub174> artiq/master 28c4d8c Sebastien Bourdeauducq: applets: attempt at fixing embedding bugs on Windows
<bb-m-labs> build #258 of artiq is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/258 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<whitequark> failed 33 minutes into the build. this is better!
<whitequark> c:\slave64\miniconda\conda-bld\work\qt-everywhere-opensource-src-5.5.1\qtimageformats\src\3rdparty\libwebp\src\dsp\upsampling_sse2.c : fatal error C1083: Cannot open compiler generated file: '': Invalid argument
<whitequark> WHAT
<whitequark> ... did it run out of disk space or what
<whitequark> i couldn't possibly have
<whitequark> *sob*
<whitequark> everything is awful
<whitequark> I've bumped into the filename length limit
<whitequark> wait, no, I've not
<whitequark> it's trying to open the file with an empty name
<whitequark> but... why
<whitequark> ... let's assume it's transient
<whitequark> bb-m-labs: force build --props=package=qt5 conda-win64
<bb-m-labs> build forced [ETA 26m30s]
<bb-m-labs> I'll give a shout when the build finishes
ylamarre has quit [Ping timeout: 250 seconds]
<bb-m-labs> build #49 of conda-win64 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-win64/builds/49
<whitequark> nope, always fails at the same place
ylamarre has joined #m-labs
evilspirit has joined #m-labs
<sb0_> bb-m-labs, force build artiq
<bb-m-labs> build forced [ETA 3m42s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #259 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/259
<bb-m-labs> build #146 of artiq-kc705-nist_qc1 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-kc705-nist_qc1/builds/146
<bb-m-labs> build #130 of artiq-kc705-nist_qc2 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-kc705-nist_qc2/builds/130
<bb-m-labs> build #132 of artiq-pipistrello-nist_qc1 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-pipistrello-nist_qc1/builds/132
<sb0_> okay I'm in for another round of wordpad patching...
<whitequark> what for?
<sb0_> trying out my applet patch
<whitequark> just install sublime already
<whitequark> actually I think I already did
ylamarre has quit [Ping timeout: 240 seconds]
<whitequark> lol savannah is still down
<whitequark> morons
<sb0_> oooh, and another asyncio bug, it seems
ylamarre has joined #m-labs
<sb0_> mh. not exactly a bug, just some weird corner case
<sb0_> no, it's a bug. you cannot shutdown a named pipe server without a race condition
<sb0_> sigh
<sb0_> let me see if I can produce a program that causes the bug most of the time, so I can clearly complain
evilspirit has quit [Ping timeout: 240 seconds]
<GitHub163> [artiq] sbourdeauducq pushed 1 new commit to master: https://git.io/v2Jvj
<GitHub163> artiq/master 5f5427f Sebastien Bourdeauducq: protocols/pipe_ipc: work around race condition with loop.start_serving_pipe/close on Windows
<bb-m-labs> build #260 of artiq is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/260 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
ylamarre has quit [Quit: ylamarre]
<GitHub32> [misoc] enjoy-digital pushed 1 new commit to master: https://git.io/v2JU0
<GitHub32> misoc/master ddac6ed Florent Kermarrec: tools/flterm.py: another cleanup pass
<GitHub139> [misoc] enjoy-digital force-pushed master from ddac6ed to 653a990: https://git.io/LjONPA
<GitHub139> misoc/master 653a990 Florent Kermarrec: tools/flterm.py: another cleanup pass
<bb-m-labs> build #262 of artiq is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/262
rjo has quit [Read error: Connection reset by peer]
<bb-m-labs> build #261 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/261
<bb-m-labs> build #133 of artiq-pipistrello-nist_qc1 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-pipistrello-nist_qc1/builds/133
<bb-m-labs> build #131 of artiq-kc705-nist_qc2 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-kc705-nist_qc2/builds/131
<bb-m-labs> build #147 of artiq-kc705-nist_qc1 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-kc705-nist_qc1/builds/147
<bb-m-labs> build #47 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/47
<GitHub4> [artiq] sbourdeauducq pushed 1 new commit to master: https://git.io/v2JtA
<GitHub4> artiq/master 3b81dd5 Sebastien Bourdeauducq: gui: workaround for Qt failing to embed applets in hidden and detached QDockWidgets
<bb-m-labs> build #263 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/263
<bb-m-labs> build #148 of artiq-kc705-nist_qc1 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-kc705-nist_qc1/builds/148
<bb-m-labs> build #132 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/132
<bb-m-labs> build #48 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/48 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<cr1901_modern> sb0_: If you play with my current commit, you'll notice that Fit To View and Zoom To Fit aren't idempotent when toggled in succession. I know why this is/am thinking about the best way to solve it. Short version is that it has to do with the slider widths screwing up the return values from Qt-provided functions.
<sb0_> bb-m-labs: force build --props=package=pyqtgraph conda-lin64
<bb-m-labs> build forced [ETA 20m13s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #78 of conda-lin64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/78
<sb0_> so, after all this bughunt, we can run and plot flopping_f_simulation on windows ...
<sb0_> let me try talking to the core device
<sb0_> what, it works?
<sb0_> wow.
kristianpaul has quit [Quit: Reconnecting]
kristianpaul has joined #m-labs
kristianpaul has joined #m-labs
rohitksingh has quit [Ping timeout: 240 seconds]
<bb-m-labs> build #134 of artiq-pipistrello-nist_qc1 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-pipistrello-nist_qc1/builds/134
folkert has quit [*.net *.split]
zoobab has quit [*.net *.split]
siruf has quit [*.net *.split]
jaeckel has quit [*.net *.split]
folkert has joined #m-labs
early has quit [*.net *.split]
cr1901_modern has quit [*.net *.split]
zoobab has joined #m-labs
siruf has joined #m-labs
early has joined #m-labs
cr1901_modern has joined #m-labs
jaeckel has joined #m-labs
rjo has joined #m-labs
jaeckel has quit [Changing host]
jaeckel has joined #m-labs
rohitksingh has joined #m-labs
rohitksingh has quit [Ping timeout: 244 seconds]
rohitksingh has joined #m-labs
rohitksingh has quit [Quit: Leaving.]
zoobab has quit [Ping timeout: 276 seconds]
zoobab has joined #m-labs
acathla has quit [Read error: Connection reset by peer]
acathla has joined #m-labs
acathla has quit [Changing host]
acathla has joined #m-labs
zoobab has quit [Ping timeout: 276 seconds]
zoobab has joined #m-labs
zoobab has quit [Ping timeout: 276 seconds]
zoobab has joined #m-labs
zoobab has quit [Ping timeout: 248 seconds]
zoobab has joined #m-labs