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
klickverbot has joined #m-labs
mumptai has quit [Remote host closed the connection]
<cr1901_modern> rjo: The new simulator is awesome. However, being able to simulate mixed code bases is no longer possible. I recall talking to sb0 about adding verilog support using IPC, but as I recall it's not trivial to do
sandeepkr has joined #m-labs
sb0 has quit [Quit: Lost terminal]
sb0___ has joined #m-labs
<sb0___> whitequark: can the int redefinition be made a bit lighter?
<sb0___> >>> x = [int(3), int(4)]
<sb0___> >>> x
<sb0___> [int(3, width=32), int(4, width=32)]
<sb0___> it also breaks hdf5 (https://github.com/m-labs/artiq/issues/453)
<GitHub169> [artiq] sbourdeauducq pushed 1 new commit to master: https://git.io/vr9Bu
<GitHub169> artiq/master 16063ff Sebastien Bourdeauducq: conda: another attempt at platform-specific dependencies
klickverbot has quit [Ping timeout: 246 seconds]
<bb-m-labs> build #440 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/440
<bb-m-labs> build #188 of artiq-win64-test is complete: Failure [failed conda_install] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/188 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<bb-m-labs> build #707 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/707 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<GitHub155> [artiq] sbourdeauducq pushed 1 new commit to master: https://git.io/vr9RW
<GitHub155> artiq/master 4d6f53c Sebastien Bourdeauducq: conda: obviously, platform-specific dependencies are broken
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 244 seconds]
<bb-m-labs> build #441 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/441
<bb-m-labs> build #189 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/189
<bb-m-labs> build #708 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/708
<GitHub146> [artiq] sbourdeauducq pushed 1 new commit to release-1: https://git.io/vr90G
<GitHub146> artiq/release-1 6c39d93 Sebastien Bourdeauducq: do not attempt to use broken conda features
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 244 seconds]
<GitHub83> [artiq] sbourdeauducq pushed 1 new commit to master: https://git.io/vr9EB
<GitHub83> artiq/master 10267f3 Sebastien Bourdeauducq: log: use broadcast instead of sync_struct, filter on new messages only (#411)
sb0___ has quit [Quit: leaving]
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 276 seconds]
<bb-m-labs> build #442 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/442
<bb-m-labs> build #190 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/190
<bb-m-labs> build #709 of artiq is complete: Exception [exception deploy_doc] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/709 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 250 seconds]
Gurty has quit [Ping timeout: 244 seconds]
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 276 seconds]
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 272 seconds]
rohitksingh has joined #m-labs
rohitksingh has quit [Ping timeout: 240 seconds]
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 276 seconds]
rohitksingh has joined #m-labs
klickverbot has joined #m-labs
Gurty has joined #m-labs
Gurty has quit [Changing host]
Gurty has joined #m-labs
klickverbot has quit [Ping timeout: 252 seconds]
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 244 seconds]
mumptai has joined #m-labs
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 260 seconds]
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 244 seconds]
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 260 seconds]
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 244 seconds]
sandeepkr has quit [Ping timeout: 240 seconds]
kuldeep_ has quit [Ping timeout: 244 seconds]
rohitksingh has quit [Quit: Leaving.]
sandeepkr has joined #m-labs
kuldeep_ has joined #m-labs
klickverbot has joined #m-labs
kuldeep_ has quit [Quit: reboot]
klickverbot has quit [Ping timeout: 260 seconds]
sandeepkr has quit [Read error: Connection reset by peer]
kuldeep has joined #m-labs
sandeepkr has joined #m-labs
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 276 seconds]
rohitksingh has joined #m-labs
sandeepkr_ has joined #m-labs
sandeepkr_ has quit [Read error: Connection reset by peer]
sandeepkr has quit [Read error: Connection reset by peer]
sandeepkr has joined #m-labs
key2 has joined #m-labs
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 244 seconds]
rohitksingh has quit [Quit: Leaving.]
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 276 seconds]
rohitksingh has joined #m-labs
rohitksingh has quit [Quit: Leaving.]
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 244 seconds]
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 246 seconds]
rohitksingh has joined #m-labs
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 276 seconds]
rohitksingh has quit [Ping timeout: 260 seconds]
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 244 seconds]
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 258 seconds]
klickverbot has joined #m-labs
<GitHub181> [artiq] sbourdeauducq pushed 2 new commits to master: https://git.io/vr9xq
<GitHub181> artiq/master ab74956 Sebastien Bourdeauducq: dashboard: forward local log messages to docks, replace status bar (#411)
<GitHub181> artiq/master a120a09 Sebastien Bourdeauducq: gui/log: add clear button (#411)
<bb-m-labs> build #443 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/443
<bb-m-labs> build #191 of artiq-win64-test is complete: Failure [failed python_unittest] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/191 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<bb-m-labs> build #710 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/710 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
klickverbot has quit [Ping timeout: 240 seconds]
kuldeep has quit [Ping timeout: 244 seconds]
sandeepkr has quit [Ping timeout: 252 seconds]
klickverbot has joined #m-labs
<whitequark> huh, weird.
<whitequark> transient timeout?
<whitequark> bb-m-labs: force build artiq
<bb-m-labs> build forced [ETA 19m26s]
<bb-m-labs> I'll give a shout when the build finishes
kuldeep has joined #m-labs
sandeepkr has joined #m-labs
<bb-m-labs> build #444 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/444
<bb-m-labs> build #192 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/192
<bb-m-labs> build #711 of artiq is complete: Exception [exception deploy_doc] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/711
<whitequark> ok, so that one was a transient timeout
<whitequark> maybe one of the windows vms decided to update or something.
<whitequark> probably not worth doing anything about.
<whitequark> but this deploy_doc problem is weird...
<whitequark> bb-m-labs: force build artiq
<bb-m-labs> build forced [ETA 19m26s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #445 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/445
<bb-m-labs> build #193 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/193
<bb-m-labs> build #712 of artiq is complete: Exception [exception deploy_doc] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/712
<whitequark> interesting
<whitequark> bb-m-labs: force build artiq
<bb-m-labs> build forced [ETA 19m26s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #446 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/446
<bb-m-labs> build #194 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/194
<bb-m-labs> build #713 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/713
<whitequark> bizarre. "mingw-get-setup.exe is not a valid Win32 application"
<whitequark> and I can get it running on a win7 VM I have locally
<whitequark> amazing.
<whitequark> it was compressed by UPX, which did something stupid, which broke it on 64-bit Windows.
<GitHub85> [artiq] sbourdeauducq pushed 3 new commits to master: https://git.io/vrHfj
<GitHub85> artiq/master 7851391 Sebastien Bourdeauducq: artiq_compile: adapt to code changes
<GitHub85> artiq/master 0faa2d5 Sebastien Bourdeauducq: language/environment: autoset scale for common units. Closes #448
<GitHub85> artiq/master 8b556ef Sebastien Bourdeauducq: language/environment: be more verbose in NumberValue unit/scale documentation (#448)
<GitHub86> [artiq] sbourdeauducq pushed 1 new commit to release-1: https://git.io/vrHJf
<GitHub86> artiq/release-1 b57b1dd Sebastien Bourdeauducq: language/environment: be more verbose in NumberValue unit/scale documentation (#448)
<GitHub144> [artiq] sbourdeauducq pushed 1 new commit to master: https://git.io/vrHJ8
<GitHub144> artiq/master 55fdfc6 Sebastien Bourdeauducq: gui/log: fix clearing multi-line messages
<bb-m-labs> build #447 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/447
<whitequark> hm, no, keeps breaking in other ways.
<bb-m-labs> build #195 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/195
<whitequark> bb-m-labs: force build --props=package=libgit2 conda-all
<bb-m-labs> The build has been queued, I'll give a shout when it starts
<GitHub163> [conda-recipes] whitequark pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/f671496438e84c8c00bce59ca90bdfe4f596521d
<GitHub163> conda-recipes/master f671496 whitequark: libgit2: install DLL in the proper place (Library/bin).
<bb-m-labs> build #714 of artiq is complete: Exception [exception deploy_doc] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/714 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<whitequark> sb0: should we attempt installation of the libusb kernel driver through conda?
<GitHub126> [conda-recipes] whitequark pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/8daccdc41602d6c9327c688e8d2e5792e28c7eb9
<GitHub126> conda-recipes/master 8daccdc whitequark: libusb: add Windows support.
<whitequark> bb-m-labs: force build --props=package=libusb conda-win32
<bb-m-labs> build #91 forced
<bb-m-labs> I'll give a shout when the build finishes
<whitequark> bb-m-labs: force build --props=package=libusb conda-win64
<bb-m-labs> build #122 forced
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #91 of conda-win32 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-win32/builds/91
<bb-m-labs> build #122 of conda-win64 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-win64/builds/122
<bb-m-labs> build #448 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/448
<bb-m-labs> build #57 forced
<bb-m-labs> I'll give a shout when the build finishes
<whitequark> bb-m-labs: force build --props=package=libusb conda-win32
<GitHub180> [conda-recipes] whitequark force-pushed master from 8daccdc to 27715d9: https://github.com/m-labs/conda-recipes/commits/master
<GitHub180> conda-recipes/master 27715d9 whitequark: libusb: add Windows support.
<bb-m-labs> The build has been queued, I'll give a shout when it starts
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
<GitHub5> [conda-recipes] whitequark pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/1906d0ff94ea11e904f3aada2c78281708eda11f
<GitHub5> conda-recipes/master 1906d0f whitequark: libgit2: change -DCMAKE_INSTALL_PREFIX too.
<bb-m-labs> build #123 of conda-win64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-win64/builds/123
<bb-m-labs> build #159 of conda-lin64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/159
<bb-m-labs> build #92 of conda-win32 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-win32/builds/92
<bb-m-labs> build #57 of conda-all is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-all/builds/57
<bb-m-labs> build forced [ETA 2m54s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #93 of conda-win32 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-win32/builds/93
<bb-m-labs> build #196 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/196
<bb-m-labs> build #715 of artiq is complete: Exception [exception deploy_doc] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/715 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<whitequark> bb-m-labs: force build --props=package=libusb conda-win32
<bb-m-labs> build forced [ETA 2m54s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #94 of conda-win32 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-win32/builds/94
<rjo> whitequark: about the doc upload failure: no idea what the problem is exactly. but it may (or may not) be triggered by the new directory (_sources).
<whitequark> i think i'm doing tree removal wrong.
<rjo> i also had to manually update the logo a while ago. either the doc build or the file syncing did not notice the logo change.
<whitequark> it should be done in reverse depth first order, but i just do it however walktree gives me the files
<whitequark> and it seems like my assumptions about walktree are incorrect.
<whitequark> bb-m-labs: force build --props=package=libusb conda-win64
<bb-m-labs> build forced [ETA 2m57s]
<bb-m-labs> I'll give a shout when the build finishes
<whitequark> re logo: that's weird.
<rjo> maybe sshfs + rsync?
<bb-m-labs> build #124 of conda-win64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-win64/builds/124
<whitequark> FUSE is extremely fragile.
<rjo> yes. i think it was actually on the build slaves. maybe sphinx is dumb.
<whitequark> if you have a network failure, then what happens is all your processes are stuck in iowait
<rjo> sure. pick your poison.
<whitequark> plain scp would work here, but i tried avoiding shelling out.
<whitequark> since, well, it's also fragile, but less so.
<whitequark> i actually think it's enough to sort directories in reverse alphabetical order for this.
<whitequark> ok. today was not meant for me to make mingw work.
<whitequark> it consistently fails to download archives from the buildbot, which is very baffling, because doing that from my home works
<whitequark> so it's not sourceforce's broken mirror selection or something, assuming it treats all HK IPs the same
<whitequark> and I cannot upload the archived installation of mingw that I have because this ADSL has such bad QoS that uploading anything over 1MB timeouts; no acks come back
<rjo> bufferbloat?
<whitequark> possibly
<GitHub138> [conda-recipes] whitequark pushed 2 new commits to master: https://github.com/m-labs/conda-recipes/compare/1906d0ff94ea...9fe47acb997b
<GitHub138> conda-recipes/master c9cae50 whitequark: libssh2: install DLL in the proper place (Library/bin).
<GitHub138> conda-recipes/master 9fe47ac whitequark: libftdi: add Windows support.
<whitequark> it seems like what happens is that it has a shared medium (the copper wire) and the outgoing packets hog that medium
<whitequark> well, now that I recall how ADSL works, that's technically incorrect, as it uses two bands. hm. no idea why it breaks, then.
<rjo> sidestory: yesterday on the train i was "borrowing" somebody else's MAC address. and obviously TCP sessions got reset all the time. but mosh worked flawlessly.
<whitequark> they really need to implement non-text tunneling in mosh (it's on the roadmap)
<whitequark> I've seen it many times that on airport wifi they didn't even bother to gate udp with the nag screen
<whitequark> bb-m-labs: force build --props=package=libgit2 conda-all
<bb-m-labs> build forced [ETA 4m32s]
<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> build forced [ETA 4m32s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #95 of conda-win32 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-win32/builds/95
<bb-m-labs> build #125 of conda-win64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-win64/builds/125
<bb-m-labs> build #160 of conda-lin64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/160
<bb-m-labs> build #58 of conda-all is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-all/builds/58
<bb-m-labs> build #96 of conda-win32 is complete: Failure [failed anaconda_upload] Build details are at http://buildbot.m-labs.hk/builders/conda-win32/builds/96
<bb-m-labs> build #161 of conda-lin64 is complete: Failure [failed anaconda_upload] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/161
<bb-m-labs> build #126 of conda-win64 is complete: Failure [failed anaconda_upload] Build details are at http://buildbot.m-labs.hk/builders/conda-win64/builds/126
<bb-m-labs> build #59 of conda-all is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/conda-all/builds/59
<whitequark> bb-m-labs: force build --props=package=libssh2 conda-all
<bb-m-labs> build forced [ETA 3m56s]
<bb-m-labs> I'll give a shout when the build finishes
<GitHub88> [conda-recipes] whitequark pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/25f754112e9c8640d2d5c591d2018f71cbcc8bff
<GitHub88> conda-recipes/master 25f7541 whitequark: libssh2: bump.
<bb-m-labs> build #97 of conda-win32 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-win32/builds/97
<bb-m-labs> build #127 of conda-win64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-win64/builds/127
<bb-m-labs> build #162 of conda-lin64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/162
<bb-m-labs> build #60 of conda-all is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-all/builds/60
klickverbot has quit [Ping timeout: 240 seconds]
<whitequark> bb-m-labs: force build --props=package=libftdi conda-win32
<bb-m-labs> build forced [ETA 1m33s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #98 of conda-win32 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-win32/builds/98
<whitequark> oh, that also needs mingw, since I'm using the mingw libusb... hrm
<GitHub127> [buildbot-config] whitequark pushed 1 new commit to master: https://github.com/m-labs/buildbot-config/commit/0750483d29da90b563c4a9fb0494796fad3e2d71
<GitHub127> buildbot-config/master 0750483 whitequark: Attempt to crudely delete files in reverse depth first order.
bb-m-labs has quit [Quit: buildmaster reconfigured: bot disconnecting]
bb-m-labs has joined #m-labs
<whitequark> bb-m-labs: force build artiq
<bb-m-labs> build #716 forced
<bb-m-labs> I'll give a shout when the build finishes
klickverbot has joined #m-labs
<bb-m-labs> build #449 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/449
<bb-m-labs> build #197 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/197
<bb-m-labs> build #716 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/716
<whitequark> rjo: that worked.
<mumptai> if i want a misoc design running only from bram, without a sdram, the soc_core is the place to start from?
<rjo> yes. integrated_rom_size and integrated_main_ram_size
<rjo> don't even need the main_ram necessarily.
<mumptai> great, then i'll continue digging around the software ;)
sandeepkr has quit [Ping timeout: 252 seconds]