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
ohsix has quit [Ping timeout: 260 seconds]
<sb0> whitequark, unittests should be self-contained. right now test_dma_playback_time fails if another test that records the trace hasn't been run before
<sb0> and it just happens to be run before by accident when you run all the tests ...
<sb0> whitequark, python -m unittest test_rtio.DMATest.test_dma_record_time test_rtio.DMATest.test_dma_playback_time -v crashes the core device
<sb0> so many bugs jesus fuck
<GitHub> [artiq] sbourdeauducq commented on issue #712: I got 1.53µs in my test, and I could bring it down to 1.37µs. https://github.com/m-labs/artiq/issues/712#issuecomment-295047395
<GitHub> [artiq] sbourdeauducq opened issue #722: intermittent core device crash when running test_dma_record_time https://github.com/m-labs/artiq/issues/722
<sb0> get_handle → dma_retrieve → DmaPlaybackRequest/DmaPlaybackReply ... could those be more consistently named?
<GitHub> [artiq] sbourdeauducq pushed 3 new commits to master: https://github.com/m-labs/artiq/compare/41c4de45563c...fe05aede7876
<GitHub> artiq/master fe05aed Sebastien Bourdeauducq: firmware: DmaPlayback → DMARetrieve
<GitHub> artiq/master badbd72 Sebastien Bourdeauducq: manual: update example to use DMA handle API
<GitHub> artiq/master e8f7f8e Sebastien Bourdeauducq: DMA: speed up playback...
<sb0> rjo, ping
klickverbot has quit [Ping timeout: 240 seconds]
rohitksingh_work has joined #m-labs
<whitequark> sb0: (self-contained) yes, of course, that wasn't done deliberately
ohsix has joined #m-labs
mumptai has joined #m-labs
<GitHub190> [rust] whitequark created artiq-1.18.0 (+2302 new commits): https://github.com/m-labs/rust/compare/ec356bb1a765^...402cf05192d3
<GitHub190> rust/artiq-1.18.0 b2cf6df Simonas Kazlauskas: Add intrinsics & target features for rd{rand,seed}
<GitHub190> rust/artiq-1.18.0 4495f7e bluecereal: Update if-let.md...
<GitHub190> rust/artiq-1.18.0 ec356bb Alex Burka: rustdoc: fix doctests with non-feature crate attrs
<GitHub> [conda-recipes] whitequark pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/f4eb2fb4f1c1315e21cb46c8c3d1798d20a08970
<GitHub> conda-recipes/master f4eb2fb whitequark: rustc: update to 0.18.0.
<whitequark> bb-m-labs: force build --props=package=rustc conda-lin64
<bb-m-labs> build #290 forced
<bb-m-labs> I'll give a shout when the build finishes
<whitequark> sb0: I don't understand, shouldn't the lab CPU be fast?
<whitequark> so far it seems slower than the CPU in my laptop
<whitequark> oh, no one gave the VMs more VCPUs
mumptai has quit [Remote host closed the connection]
<sb0> why are we updating rustc again?
<sb0> if that really needs to be done, please update the "build from source" instructions in the doc
<whitequark> because it's two months old?
<whitequark> and I suspect it will fix one of the bugs, anyway
<whitequark> oh, hm, no, it's not slow, it's about exactly as fast as the one in my laptop
<sb0> fixing some user-visible bug is a good reason, two months old doesn't really matter
<whitequark> it does
<whitequark> we have a fork of rust and we use lots of unstable features
<whitequark> in both cases it's far easier to fix small amounts of breakage as it rolls in, as opposed to screwing with it for several days straight every half year
<bb-m-labs> build #290 of conda-lin64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/290
<sb0> but is it really the best thing to do right now? smoltcp is still at 25k/s, doesn't support keepalive, lots of compiler and runtime bugs, artiq tools don't start on windows anymore, etc.
<GitHub> [conda-recipes] whitequark pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/eda00a7b489444a857f58b6d9759b95dede771ef
<GitHub> conda-recipes/master eda00a7 whitequark: rust-core-or1k: update to 0.18.0.
<whitequark> we've almost spent longer discussing this than the time I spent touching rustc
<whitequark> bb-m-labs: force build --props=package=rust-core-or1k conda-lin64
<bb-m-labs> build forced [ETA 47m09s]
<bb-m-labs> I'll give a shout when the build finishes
<sb0> well, make sure the doc is updated and the drtio firmwares still work
<whitequark> yes, I've updated the doc long ago...
<bb-m-labs> build #291 of conda-lin64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/291
<sb0> whitequark, the doc says "git clone -b artiq-1.16.0 https://github.com/m-labs/rust" and you just created artiq-1.18.0. so no.
<whitequark> I haven't said that I pushed those changes
<whitequark> and I didn't do that because the buildbot build would have immediately failed
<whitequark> I'm now checking drtio_satellite and after that I'll push
<sb0> well the buildbot github trigger is also broken...
<whitequark> oh right.
<GitHub> [artiq] whitequark pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/db494967c5b871768b9dca7cd9d008383d9bcbfe
<GitHub> artiq/master db49496 whitequark: firmware use Rust 0.18.0.
bb-m-labs has quit [Quit: buildmaster reconfigured: bot disconnecting]
bb-m-labs has joined #m-labs
<whitequark> sb0: fixed.
<whitequark> bb-m-labs: force build artiq
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #1467 forced
<bb-m-labs> build #1467 of artiq is complete: Failure [failed lit_test] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1467
<whitequark> what
<whitequark> oh, *great*
<whitequark> leave it to conda to fuck up a perfectly working compiler
<whitequark> it does something to paths inside rustc and rustc doesn't work anymore.
<whitequark> (rustc obviously did work before because the rustc build process involves running a stage1 rustc on stage2 rustc...)
<whitequark> sb0: do you happen to remember what was the incantation needed to let conda-build keep binaries intact?
<whitequark> sb0: ok, so conda-build changed the default for detect_binary_files_with_prefix from false to true in 2.0
<whitequark> this means that a large amount of packages we currently have in repos will probably not work once they're rebuilt
<whitequark> if rustc is any indication, at least
<GitHub> [conda-recipes] whitequark pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/f52c329afc0f39094ecd8792b500c04c341d2025
<GitHub> conda-recipes/master f52c329 whitequark: rustc: tell conda to leave binaries alone.
<GitHub> [conda-recipes] whitequark pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/0e8d2c96e324246764c40e728e134f56e161f5e0
<GitHub> conda-recipes/master 0e8d2c9 whitequark: rustc, rust-core-or1k: bump.
<whitequark> bb-m-labs: force build --props=package=rustc conda-lin64
<bb-m-labs> build #292 forced
<bb-m-labs> I'll give a shout when the build finishes
<whitequark> bb-m-labs: force build --props=package=rust-core-or1k conda-lin64
<bb-m-labs> The build has been queued, I'll give a shout when it starts
<sb0> whitequark, thanks, what did you change to fix the github hook?
<whitequark> sb0: edited the hmac invocation in /usr/lib/python2.7/dist-packages/buildbot/status/web/hooks/github.py to pass arguments as bytearray()s
<whitequark> (I hope that by the time debian gets a new buildbot, it will also fix that)
<whitequark> probably will happen when squeeze goes stable, anyway.
<GitHub> [artiq] whitequark closed issue #721: github buildbot triggers broken https://github.com/m-labs/artiq/issues/721
<bb-m-labs> build #292 of conda-lin64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/292
<bb-m-labs> build forced [ETA 38m04s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #293 of conda-lin64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/293
<whitequark> bb-m-labs: force build artiq
<bb-m-labs> build #1468 forced
<bb-m-labs> I'll give a shout when the build finishes
<whitequark> bb-m-labs: stop build artiq wrong
<bb-m-labs> build 1468 interrupted
<bb-m-labs> build #1468 of artiq is complete: Exception [exception interrupted conda_remove] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1468
<GitHub> [artiq] whitequark pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/5324a425493cbc40ae2628e8dc5ee04adf7c96d2
<GitHub> artiq/master 5324a42 whitequark: conda: update rust dependency.
<whitequark> fascinating
<whitequark> the webhook succeeds but it doesn't actually start a build
<whitequark> bb-m-labs: force build artiq
<bb-m-labs> build #1469 forced
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #521 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/521
<bb-m-labs> build #1469 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1469
bb-m-labs has quit [Quit: buildmaster reconfigured: bot disconnecting]
<GitHub99> [buildbot-config] whitequark pushed 1 new commit to master: https://git.io/vSxHC
<GitHub99> buildbot-config/master 3a35e96 whitequark: Replace our homegrown conda cache cleanup with `conda build purge`.
bb-m-labs has joined #m-labs
<whitequark> bb-m-labs: force build artiq
<bb-m-labs> build #1470 forced
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #522 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/522
<bb-m-labs> build #1470 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1470
<whitequark> bb-m-labs: force build --props=package=rust-core-or1k conda-lin64
<bb-m-labs> build #294 forced
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #294 of conda-lin64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/294
<whitequark> bb-m-labs: force build artiq
<bb-m-labs> build #1471 forced
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #523 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/523
<bb-m-labs> build #1471 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1471
<whitequark> wtf
<whitequark> bb-m-labs: force build artiq
<bb-m-labs> build #1472 forced
<bb-m-labs> I'll give a shout when the build finishes
rohitksingh_work has quit [Read error: Connection reset by peer]
<bb-m-labs> build #524 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/524
<bb-m-labs> build #1472 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1472
<whitequark> no, seriously, wtf?
<whitequark> I just cleaned all caches...
<whitequark> bb-m-labs: force build --props=package=rust-core-or1k conda-lin64
<bb-m-labs> build forced [ETA 3m57s]
<bb-m-labs> I'll give a shout when the build finishes
<GitHub> [artiq] whitequark pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/af20e7ede4384ea850a7d430ceb31893ba48833e
<GitHub> artiq/master af20e7e whitequark: conda: update rust dependency.
<whitequark> what a monumental waste of time conda is.
<whitequark> sb0: what's our strategy for dealing with OOM?
<whitequark> rust's collections currently do not allow to detect this (and never will), and they also do not allow to change allocators (but will do someday)
<bb-m-labs> build #295 of conda-lin64 is complete: Failure [failed anaconda_upload] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/295
<whitequark> bb-m-labs: force build --props=package=rust-core-or1k conda-lin64
<bb-m-labs> build forced [ETA 3m57s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #296 of conda-lin64 is complete: Failure [failed anaconda_upload] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/296
<whitequark> why does it build the -14 package...
<whitequark> bb-m-labs: force build --props=package=rust-core-or1k conda-lin64
<bb-m-labs> build forced [ETA 3m57s]
<bb-m-labs> I'll give a shout when the build finishes
<GitHub> [conda-recipes] whitequark pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/2671bff057d8661c0017e54b034de0cd1166e0ad
<GitHub> conda-recipes/master 2671bff whitequark: rust-core-or1k: bump.
<bb-m-labs> build #297 of conda-lin64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/297
<whitequark> bb-m-labs: force build artiq
<bb-m-labs> build #1473 forced
<bb-m-labs> I'll give a shout when the build finishes
rohitksingh has joined #m-labs
<bb-m-labs> build #525 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/525
<bb-m-labs> build #1473 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1473
<whitequark> oh ffs
<whitequark> here's the fucking dependency
<whitequark> Dependency missing in current linux-64 channels: - artiq-dev 3.0.dev py_1003+gitaf20e7ed -> rust-core-or1k 1.18.0 15
<whitequark> how is it missing exactly?
<whitequark> bb-m-labs: force build --props=package=artiq-kc705-nist_clock
<bb-m-labs> you must provide a Builder, try 'force build [--branch=BRANCH] [--revision=REVISION] [--props=PROP1=VAL1,PROP2=VAL2...] <WHICH> <REASON>'
<whitequark> bb-m-labs: force build --props=package=artiq-kc705-nist_clock conda-lin64
<bb-m-labs> build forced [ETA 3m46s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #298 of conda-lin64 is complete: Failure [failed get_output_name] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/298
<whitequark> bb-m-labs: force build --props=package=artiq-kc705-nist_clock artiq-board
<bb-m-labs> build #526 forced
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #526 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/526
<whitequark> sb0: so I can quite easily do `conda install rust-core-or1k=1.18.0=15` but it fails on the buildbot.
<whitequark> bb-m-labs: force build --props=package=artiq-kc705-nist_clock artiq-board
<bb-m-labs> build #527 forced
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #527 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/527
<whitequark> bb-m-labs: force build --props=package=artiq-kc705-nist_clock artiq-board
<bb-m-labs> build #528 forced
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #528 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/528
<whitequark> bb-m-labs: force build --props=package=artiq-kc705-nist_clock artiq-board
<bb-m-labs> build #529 forced
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #529 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/529
<whitequark> bb-m-labs: force build --props=package=artiq-kc705-nist_clock artiq-board
<bb-m-labs> build #530 forced
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #530 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/530
<whitequark> bb-m-labs: force build --props=package=artiq-kc705-nist_clock artiq-board
<bb-m-labs> build #531 forced
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #531 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/531
<whitequark> bb-m-labs: force build artiq
<bb-m-labs> build #1474 forced
<bb-m-labs> I'll give a shout when the build finishes
<whitequark> sb0: answer: sometimes conda cache can become fucked, and then it silently refuses to install packages pretending they don't exist
<whitequark> conda clena -i seems to fix it
ohsix has quit [Ping timeout: 260 seconds]
<bb-m-labs> build #532 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/532
<bb-m-labs> build #1474 of artiq is complete: Failure [failed conda_install] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1474
<whitequark> oh *wonderful*
<whitequark> another conda issue
bb-m-labs has quit [Quit: buildmaster reconfigured: bot disconnecting]
<GitHub171> [buildbot-config] whitequark pushed 1 new commit to master: https://git.io/vSpWM
<GitHub171> buildbot-config/master 40bf335 whitequark: Bring back our homegrown cache cleanup too, for good measure.
bb-m-labs has joined #m-labs
<whitequark> bb-m-labs: force build artiq
<bb-m-labs> build #1475 forced
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #533 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/533
<bb-m-labs> build #1475 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1475
<whitequark> sb0: Error while finding module specification for 'artiq.gateware.targets.kc705_dds' (ImportError: No module named 'artiq.gateware')
<whitequark> what's the fix for that?
<whitequark> bb-m-labs: force build artiq
<bb-m-labs> build #1476 forced
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #534 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/534
<bb-m-labs> build #1476 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1476
<whitequark> sb0: hang on
<whitequark> I think I know why that happens
<whitequark> Missing dependency artiq-dev, but found recipe directory, so building artiq-dev first
<whitequark> why does it think the dependency is missing...
bb-m-labs has quit [Quit: buildmaster reconfigured: bot disconnecting]
bb-m-labs has joined #m-labs
<GitHub131> [buildbot-config] whitequark pushed 1 new commit to master: https://git.io/vSpg3
<GitHub131> buildbot-config/master 2925a35 whitequark: Try cleaning conda indexes too, for good measure.
<whitequark> bb-m-labs: force build artiq
<bb-m-labs> build #1477 forced
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #535 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/535
<bb-m-labs> build #1477 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1477
klickverbot has joined #m-labs
<whitequark> sb0: I dunno.
<whitequark> let's just rollback conda-build.
<whitequark> I think the older version had less bugs and they were less bad. I have no idea what to do about these.
<sb0> whitequark, but then conda will install artiq-dev=3.0 for the release-2 build.
<sb0> they have a 2.1.10, could also try upgrading it. though they rarely fix bugs.
<whitequark> hmm.
mumptai has joined #m-labs
klickverbot has quit [Ping timeout: 258 seconds]
klickverbot has joined #m-labs
klickverbot has quit [Read error: Connection reset by peer]
klickverbot has joined #m-labs
rohitksingh has quit [Quit: Leaving.]
ohsix has joined #m-labs
siruf_ has joined #m-labs
klickverbot has quit [Ping timeout: 240 seconds]
klickverbot has joined #m-labs
mumptai has quit [Quit: Verlassend]