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
<GitHub88> [artiq] jordens pushed 1 new commit to master: https://git.io/vzx6n
<GitHub88> artiq/master 107e2fe Robert Jordens: ctlmgr: reinstate lost changes
<bb-m-labs> build #189 of artiq is complete: Success [build successful] Build details are at http://m-labs-buildserver.lan/buildbot/builders/artiq/builds/189
<bb-m-labs> build #97 of artiq-kc705-nist_qc2 is complete: Failure [failed conda_build] Build details are at http://m-labs-buildserver.lan/buildbot/builders/artiq-kc705-nist_qc2/builds/97 blamelist: Robert Jordens <jordens@gmail.com>
<GitHub191> [artiq] jordens pushed 1 new commit to master: https://git.io/vzxPC
<GitHub191> artiq/master d05d720 Robert Jordens: tests: misc fixes, cleanup
<bb-m-labs> build #190 of artiq is complete: Failure [failed conda_build] Build details are at http://m-labs-buildserver.lan/buildbot/builders/artiq/builds/190 blamelist: Robert Jordens <jordens@gmail.com>
<cr1901_modern> rjo: Hey, did you know that coloring sliders two different colors is REALLY hard (TM) w/ a custom widget. I'll get to that later so you can distinguish max from min when they reverse directions, but that's taking me deep down the Qt Rabbit Hole
<rjo> cr1901_modern: isn't there a PNG for the slider?
<rjo> cr1901_modern: OTOH exposing the direction visually is not that important.
<rjo> cr1901_modern: people can look at the spin boxes. to swap direction they have to do two drags with the mouse anyway.
<rjo> cr1901_modern: and maybe having the "stop" slider be on top (and thus the only one carrying the selection visual marker) is not that bad...
<bb-m-labs> build #12 of artiq-kc705-nist_clock is complete: Success [build successful] Build details are at http://m-labs-buildserver.lan/buildbot/builders/artiq-kc705-nist_clock/builds/12
<GitHub64> [artiq] jordens pushed 1 new commit to master: https://git.io/vzxMT
<GitHub64> artiq/master 17ac64a Robert Jordens: ctlmgr: fix the fix (107e2fe)
<bb-m-labs> build #191 of artiq is complete: Success [build successful] Build details are at http://m-labs-buildserver.lan/buildbot/builders/artiq/builds/191
<bb-m-labs> build #98 of artiq-kc705-nist_qc2 is complete: Failure [failed conda_build] Build details are at http://m-labs-buildserver.lan/buildbot/builders/artiq-kc705-nist_qc2/builds/98 blamelist: Robert Jordens <jordens@gmail.com>
<cr1901_modern> rjo: I'm wasn't aware of one? I could probably add one using Stylesheets
<cr1901_modern> wasn't aware of a PNG*
<rjo> cr1901_modern: i just vaguely remember seeing the retrievel of a theme's png in some stackoverflow question.
<rjo> retrieval
<rjo> but that may have been something else.
<cr1901_modern> Ahh, I decided not to go that route b/c the person in question was treating a QLabel and the second QSlider, and I didn't feel like that was a proper solution.
<whitequark> just use a QML style
early` has joined #m-labs
<cr1901_modern> I guess I could try a stylesheet. I had a reason for avoiding them previously, but I no longer remember what it was. Guess I'll find out
early has quit [*.net *.split]
<cr1901_modern> Oh wait... it seems QML is something different!
ylamarre has quit [Read error: Connection reset by peer]
ylamarre has joined #m-labs
<whitequark> the stylesheets are the same
<cr1901_modern> rjo: In case you are wondering, Qxt creates a dual slider by querying Qt for information about how to draw the slider widget before it actually draws, and then drawing each component of a slider one at a time, including the second slider. The same classes can be used to query whether the mouse is clicked over each widget component.
<cr1901_modern> I was trying to see if I can use te same classes (QStyle) to change the color, and so far nothing I tried has worked. So I'll try a stylesheet next and see if I can make QStyle happy with it.
ylamarre has quit [Read error: Connection reset by peer]
ylamarre has joined #m-labs
sb0__ has quit [Ping timeout: 252 seconds]
acathla` is now known as acathla
acathla has quit [Changing host]
acathla has joined #m-labs
evilspirit has joined #m-labs
<GitHub43> [artiq] jordens pushed 1 new commit to master: https://git.io/vzxj3
<GitHub43> artiq/master 6889149 Robert Jordens: analyzer: move common to artiq.protocols...
<bb-m-labs> build #14 of artiq-kc705-nist_clock is complete: Failure [failed conda_build] Build details are at http://m-labs-buildserver.lan/buildbot/builders/artiq-kc705-nist_clock/builds/14 blamelist: Robert Jordens <jordens@gmail.com>
<bb-m-labs> build #99 of artiq-kc705-nist_qc2 is complete: Success [build successful] Build details are at http://m-labs-buildserver.lan/buildbot/builders/artiq-kc705-nist_qc2/builds/99
ylamarre has quit [Ping timeout: 260 seconds]
ylamarre has joined #m-labs
evilspirit has quit [Ping timeout: 250 seconds]
evilspirit has joined #m-labs
ylamarre has quit [Quit: ylamarre]
mumptai has joined #m-labs
sj_mackenzie has joined #m-labs
rohitksingh has joined #m-labs
evilspirit has quit [Ping timeout: 276 seconds]
sb0 has joined #m-labs
sb0 has quit [Quit: Leaving]
sb0__ has joined #m-labs
<sb0__> whitequark: have you updated the buildbot test so it doesn't use setup.py?
evilspirit has joined #m-labs
rohitksingh has quit [Quit: Leaving.]
sb0__ has quit [Quit: Page closed]
evilspirit has quit [Ping timeout: 272 seconds]
sj_mackenzie has quit [Ping timeout: 240 seconds]
<whitequark> sb0: not yet, let me
<whitequark> sb0: ah, I now remember why--which method do you want me to use? I'm not sure which one works properly the most of the time
<GitHub94> [artiq] jordens pushed 1 new commit to increase-runtime-size: https://git.io/vzhhu
<GitHub94> artiq/increase-runtime-size 10d78a5 Robert Jordens: flash: grow runtime limit to 512 kB
rjo_ has joined #m-labs
<rjo_> mithro: consider http://paginas.fe.up.pt/~ee06211/doku.php?id=digilent_atlys#interfacing_with_the_onboard_numonyx_n25q128 . i don't think everything in that text is correct but it might be related to your problem.
sb0___ has joined #m-labs
<sb0___> whitequark: what are the options?
<sb0___> setting PYTHONPATH sounds pretty robust imo
<rjo> there are so many places where we try to start subprocesses in similar environments than the parent. why don't we add a little "artiq_start.py" that sets sys.path and then behaves like "python -m". artiq_start would be run by filename (and each subprcess starter needs to determine where "its" artiq_start.py is.
* whitequark will implement whatever you agree on, just do agree on something
<rjo> and PYTHONPATH can be tricky imho. you would need to prepend.
<rjo> sb0___: ok to merge artiq/increase-runtime-size? whitequark: can you imagine the runtime ever growing beyond 512 kB? even with an ocaml+haskel+rust networks stack and corresponding support?
<rjo> it seems more likely that the flash_sotrage grows a lot and beyond a sector.
<rjo> and why is the kc705 runtime also that large? it should not have ppp.
<rjo> ah. through the PPP preproc defs...