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
mumptai_ has quit [Remote host closed the connection]
AceChen has joined #m-labs
AceChen has quit [Quit: leaving]
AceChen has joined #m-labs
<GitHub109> [artiq] sbourdeauducq pushed 1 new commit to rtio-sed: https://github.com/m-labs/artiq/commit/20d79c930c4f5b1fecbaaf08fae94170a9d17555
<GitHub109> artiq/rtio-sed 20d79c9 Sebastien Bourdeauducq: drtio: use SED and input collector
<sb0> bb-m-labs, force build --branch=rtio-sed artiq
<bb-m-labs> build forced [ETA 31m57s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #1683 of artiq is complete: Failure [failed python_unittest_1] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1683
<sb0> bb-m-labs, force build --branch=rtio-sed artiq
<bb-m-labs> build forced [ETA 31m57s]
<GitHub139> [artiq] sbourdeauducq pushed 1 new commit to rtio-sed: https://github.com/m-labs/artiq/commit/e430d04d3ffbb7636018632b0a3a535e7ad4a994
<GitHub139> artiq/rtio-sed e430d04 Sebastien Bourdeauducq: drtio: remove obsolete import
<bb-m-labs> I'll give a shout when the build finishes
sb0 has quit [Quit: Leaving]
<bb-m-labs> build #783 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/783
<bb-m-labs> build #1684 of artiq is complete: Failure [failed python_unittest_2] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1684
sb0 has joined #m-labs
<sb0> rjo, hmm it seems "pld load" is broken now
<sb0> on sayma
<sb0> ah no, nevermind
<sb0> my bitfile is garbage and openocd simply displays "failed to load" in this case, instead of a more explicit message
<cr1901_modern> bin vs bit strikes again?
<cr1901_modern> or is it literal garbage?
<sb0> html 404 page
<sb0> oh amazing, so on the first board yes the second flash is broken
<sb0> on the second one, loading the FPGA fucks the JTAG chain
<sb0> loaded file bscan_spi_xcku040-sayma.bit to pld device 0 in 1s 373430us
<sb0> Error: JTAG scan chain interrogation failed: all zeroes
<sb0> trying the third board
<sb0> pfff
cjbe has joined #m-labs
cjbe has quit [Client Quit]
<sb0> also this "scan chain interrogation failed" on the third one ...
<sb0> what else
cjbe has joined #m-labs
cjbe has quit [Quit: cjbe]
<sb0> anyway, the three saymas are connected and powered now
rohitksingh has joined #m-labs
cjbe has joined #m-labs
cjbe has quit [Quit: cjbe]
sb0 has quit [Quit: Leaving]
<GitHub97> [smoltcp] whitequark pushed 2 new commits to master: https://git.io/vdTvQ
<GitHub97> smoltcp/master 43cc132 whitequark: Fix a typo in documentation.
<GitHub97> smoltcp/master 1a81029 whitequark: Fix two issues that may cause TCP sockets to be polled too late....
<travis-ci> m-labs/smoltcp#261 (master - 1a81029 : whitequark): The build passed.
mumptai has joined #m-labs
sb0 has joined #m-labs
cjbe has joined #m-labs
cjbe has quit [Quit: cjbe]
cjbe has joined #m-labs
cjbe has quit [Quit: cjbe]
cjbe has joined #m-labs
cjbe has quit [Client Quit]
cjbe has joined #m-labs
cjbe has quit [Quit: cjbe]
cjbe has joined #m-labs
cjbe has quit [Quit: cjbe]
<rjo> sb0: i'll have a look.
<rjo> sb0: also from some other data i suspect there may have been some bad upstream changes.
rohitksingh has quit [Quit: Leaving.]
<GitHub132> [smoltcp] whitequark pushed 1 new commit to master: https://git.io/vdTqZ
<GitHub132> smoltcp/master c73721a whitequark: Completely redo the logic of TCP socket polling....
Gurty has quit [Ping timeout: 240 seconds]
<GitHub187> [smoltcp] whitequark pushed 3 new commits to master: https://git.io/vdTqR
<GitHub187> smoltcp/master 7362e1a whitequark: A few cosmetic changes to TCP socket trace messages....
<GitHub187> smoltcp/master b7b4877 whitequark: Fix an embarassing relative/absolute time mismatch in examples.
<GitHub187> smoltcp/master 6f5ae33 whitequark: Add a keep-alive and timeout demo to the examples.
<travis-ci> m-labs/smoltcp#262 (master - c73721a : whitequark): The build passed.
<travis-ci> m-labs/smoltcp#263 (master - 6f5ae33 : whitequark): The build passed.
Gurty has joined #m-labs
Gurty has quit [Changing host]
Gurty has joined #m-labs
<whitequark> sb0: testing keepalive/timeout
<whitequark> there were a few bugs around the core functionality covered by unit test
<sb0> cool
<whitequark> also i got some mail from webpki folks
<whitequark> brian, who's writing a safe tls impl in rust
<whitequark> apparently he likes smoltcp a lot
<sb0> ok, what about?
<whitequark> elaborate?
<whitequark> sb0: ugh
<whitequark> I want to update ou rustc
<whitequark> somewhere on the way smoltcp started using features and library assumptions from 1.20
<sb0> whitequark, what was the email about?
<sb0> whitequark, isn't it working on artiq already?
<sb0> without those features?
<whitequark> oh, we discussed his library for safe(r) parsing of data
<whitequark> but smoltcp already uses fuzzing to eliminate those parsing bugs
<whitequark> and more
<whitequark> well it doesn't anymore
<whitequark> somewhere while implementing the last bits I introduced those
<whitequark> let me see what's more of a pain, updating rustc or reverting parts of smoltcp
<sb0> what last bits? are those features very important?
<whitequark> oh and there was the associated constants PR that also depends on 1.20...
<whitequark> hmm
<sb0> _florent_, have you been able to install/compile artiq? do you need help?
<GitHub142> [smoltcp] whitequark pushed 1 new commit to master: https://git.io/vdTZw
<GitHub142> smoltcp/master 081851d whitequark: Clarify README paragraph about features....
<travis-ci> m-labs/smoltcp#264 (master - 081851d : whitequark): The build passed.
<GitHub174> [rust] whitequark created artiq-1.20.0 (+2444 new commits): https://github.com/m-labs/rust/compare/4bcfbc36c672^...3ed30e3de7a0
<GitHub174> rust/artiq-1.20.0 85049e5 Djzin: avoid recursion
<GitHub174> rust/artiq-1.20.0 5702f43 Djzin: a new approach; ditch xor cuteness and maximize cache locality
<GitHub174> rust/artiq-1.20.0 4bcfbc3 Djzin: speed up mem::swap
<whitequark> we;ll that was.. painless
<GitHub> [conda-recipes] whitequark pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/d945891afc370ca13cf87ae1da52fba23605d439
<GitHub> conda-recipes/master d945891 whitequark: rustc, rust-core-or1k: update to 1.20.0.
<GitHub> [conda-recipes] whitequark pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/a219226b51fcd47bdb30eefd72ce8c53f7599bea
<GitHub> conda-recipes/master a219226 whitequark: rustc: don't build docs.
<GitHub> [conda-recipes] whitequark pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/41fe7bccdb45a596fc1bed4848e9940d14d713a6
<GitHub> conda-recipes/master 41fe7bc whitequark: rust-core-or1k: update for liballoc/libcollections merge.
<whitequark> bb-m-labs: force build --props=package=rustc conda-lin64
<bb-m-labs> build forced [ETA 37 seconds]
<bb-m-labs> I'll give a shout when the build finishes
<GitHub121> [rust] whitequark force-pushed artiq-1.20.0 from 3ed30e3 to bf2656a: https://github.com/m-labs/rust/commits/artiq-1.20.0
<GitHub121> rust/artiq-1.20.0 1dffdb2 whitequark: Make i128 optional in libcore.
<GitHub121> rust/artiq-1.20.0 7dc3371 whitequark: Add #[cfg(target_family="none")] support to libpanic_*.
<GitHub121> rust/artiq-1.20.0 88f1782 whitequark: Add mini-libc (only works on OR1K).
<bb-m-labs> build #320 of conda-lin64 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/320
<whitequark> ummmmm sigkill?
<whitequark> who killed my build?
<whitequark> it's not an OOM...
<whitequark> bb-m-labs: force build --props=package=rustc conda-lin64
<bb-m-labs> build forced [ETA 37 seconds]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #321 of conda-lin64 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/321
<whitequark> sb0: any idea wtf is happening here?
<whitequark> oh *facepalm*
<whitequark> this build process runs in a VM, not on the host
<whitequark> it is an OOM
<travis-ci> batonius/smoltcp#84 (default_route - 601685e : Egor Karavaev): The build passed.
<whitequark> bb-m-labs: force build --props=package=rustc conda-lin64
<bb-m-labs> build forced [ETA 37 seconds]
<bb-m-labs> I'll give a shout when the build finishes
<GitHub95> [smoltcp] whitequark commented on issue #44: Quick comment so this doesn't sit idle: can you please add a `struct Ipv4Cidr { addr, mask }` and `enum IpCidr { Ipv4(Ipv4Cidr) }`, just like it's done for `struct Ipv4Addr` and `enum IpAddr`? I'd really like smoltcp to gain these abstractions eventually, anyway. https://git.io/vdTB5
<GitHub42> [smoltcp] whitequark commented on issue #44: Oh sorry I already wrote this comment and forgot about it! Let me take another look. https://git.io/vdTBb
<GitHub53> [smoltcp] whitequark commented on issue #44: Oh sorry I already wrote this comment and forgot about it! If you don't want to deal with this I can implement it myself, no big deal. https://git.io/vdTBb
<bb-m-labs> build #322 of conda-lin64 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/322
<GitHub144> [smoltcp] batonius commented on issue #44: My first thought was to implement some kind of `Cidr` data type, which is handy to have anyway, but I decided against it because it doesn't fit here conceptually. Specifically, 'mask length' is an attribute of an address assigned to an interface, not of the default route, which is a bare IP address, so it would be wrong to bundle them together in a single `Cidr` value. That means the right approach shoul
<GitHub106> [sinara] gkasprow pushed 2 new commits to master: https://github.com/m-labs/sinara/compare/59a7fe8c6157...e1b238c293e3
<GitHub106> sinara/master 276caf8 Greg: fixed #322, still length matching needed
<GitHub106> sinara/master e1b238c Greg: Merge branch 'master' of https://github.com/m-labs/sinara
cjbe has joined #m-labs
cjbe has quit [Client Quit]
<GitHub44> [smoltcp] whitequark commented on issue #44: > That means the right approach should probably involve changing EthernetInterface::new to accept a slice of IpCidrs instead of IpAdddresss and require an IpAddress of the default gateway as well, but I really didn't want to change public API.... https://git.io/vdT27
<GitHub> [conda-recipes] whitequark pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/f85ee62f08dce722988e5d3a2ea53023b42af9cf
<GitHub> conda-recipes/master f85ee62 whitequark: rustc: fix build script.
<whitequark> bb-m-labs: force build --props=package=rustc conda-lin64
<bb-m-labs> build forced [ETA 37 seconds]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #323 of conda-lin64 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/323
<GitHub> [conda-recipes] whitequark pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/3c753a4a21f2e1815fccd527bccf244e6e17cfb4
<GitHub> conda-recipes/master 3c753a4 whitequark: rustc: fix build script for real.
<whitequark> bb-m-labs: force build --props=package=rustc conda-lin64
<bb-m-labs> build forced [ETA 37 seconds]
<bb-m-labs> I'll give a shout when the build finishes
mumptai has quit [Remote host closed the connection]
<travis-ci> batonius/smoltcp#85 (default_route - 31202ff : Egor Karavaev): The build passed.
<travis-ci> batonius/smoltcp#86 (default_route - adcf30f : Egor Karavaev): The build passed.
<GitHub25> [smoltcp] batonius commented on issue #44: Done. https://git.io/vdT6P
<GitHub71> [artiq] whitequark commented on issue #662: Timeouts and keepalive turned on, and tested by adding a `-A OUTPUT -d $CORE_DEVICE -j DROP` rule to iptables. https://github.com/m-labs/artiq/issues/662#issuecomment-331746235
<GitHub147> [artiq] whitequark closed issue #662: smoltcp checklist https://github.com/m-labs/artiq/issues/662
<bb-m-labs> build #324 of conda-lin64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/324
<whitequark> bb-m-labs: force build --props=package=rust-core-or1k conda-lin64
<bb-m-labs> build forced [ETA 18m11s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #325 of conda-lin64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/325
<GitHub148> [artiq] whitequark pushed 2 new commits to master: https://github.com/m-labs/artiq/compare/57b12abf1ef7...c00b3fe8cd4c
<GitHub148> artiq/master c00b3fe whitequark: firmware: update smoltcp.
<GitHub148> artiq/master 7799413 whitequark: firmware: update Rust from 1.18.0 to 1.20.0.
<GitHub46> [smoltcp] whitequark commented on pull request #44 adcf30f: Nit: I think `MT` used to mean something but now it can be just replaced with `T` everywhere here (so `GatewayT`). https://git.io/vdTiD
<GitHub106> [smoltcp] whitequark commented on pull request #44 adcf30f: I assume there's an `impl Into<Option<T>> for Option<Into<T>>` or something like it? https://git.io/vdTiM
<GitHub87> [smoltcp] whitequark commented on pull request #44 adcf30f: Prefix length, not mask length; the mask is as long as the IP address, but has only as many zeroes as the prefix length. https://git.io/vdTiS
<GitHub91> [smoltcp] whitequark commented on pull request #44 adcf30f: Nit: just `contains`. https://git.io/vdTiy
<GitHub69> [smoltcp] whitequark commented on pull request #44 adcf30f: Nit: I think `address` sounds nicer, and see above on mask_len. https://git.io/vdTiH
<GitHub40> [smoltcp] whitequark commented on pull request #44 adcf30f: This function doesn't seem very useful as the valid ranges of prefix lengths depend on the address. https://git.io/vdTi9
<GitHub176> [smoltcp] whitequark commented on pull request #44 adcf30f: Since this field is `pub`, the struct needs an `is_valid()` method, which should be checked in `set_protocol_addrs`. https://git.io/vdTid
<GitHub1> [smoltcp] whitequark commented on pull request #44 adcf30f: I've been uncomfortable calling this data structure "CIDR" for a while but I just realized what the proper name for it would be: `IpSubnet`! That makes much more sense. I'm sorry for having you change everything. https://git.io/vdTiQ
<GitHub36> [smoltcp] whitequark commented on pull request #44 adcf30f: Nit: the phrase "default gateway" is a remnant of the times where a single LAN segment would conceivably have more than one gateway. At this point it's an anachronism (like classful networks!), let's call this just "gateway". Also applies elsewhere in this PR. https://git.io/vdTi5
<GitHub172> [smoltcp] whitequark commented on pull request #44 adcf30f: Nit: just `address`. https://git.io/vdTi7
<GitHub59> [smoltcp] whitequark closed pull request #45: Uncomment associated constants (master...assoc_const) https://git.io/v5jmX
<GitHub65> [smoltcp] whitequark pushed 1 new commit to master: https://git.io/vdTib
<GitHub65> smoltcp/master 0454c3f Egor Karavaev: Uncomment associated constants.
<GitHub164> [smoltcp] whitequark commented on issue #45: (We've updated our internal fork.) https://git.io/vdTiN
<travis-ci> m-labs/smoltcp#268 (master - 0454c3f : Egor Karavaev): The build passed.
<GitHub163> [smoltcp] whitequark pushed 1 new commit to master: https://git.io/vdTPe
<GitHub163> smoltcp/master 2d31ef9 whitequark: Add some docs.
<travis-ci> m-labs/smoltcp#269 (master - 2d31ef9 : whitequark): The build passed.
<bb-m-labs> build #784 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/784
<bb-m-labs> build #572 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/572
<bb-m-labs> build #1685 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1685