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
<bb-m-labs> build #582 of artiq-win64-test is complete: Failure [failed conda_install] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/582 blamelist: whitequark <whitequark@whitequark.org>
<bb-m-labs> build #1701 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1701 blamelist: whitequark <whitequark@whitequark.org>
<GitHub35> [artiq] whitequark pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/e59b301a3be630cc16754cfb2815c6d37a8ba4f5
<GitHub35> artiq/master e59b301 whitequark: compiler: disallow op= on mutable values (fix #835)....
<GitHub17> [artiq] whitequark closed issue #835: Compiler crash on list addition https://github.com/m-labs/artiq/issues/835
<GitHub97> [artiq] whitequark commented on issue #835: Now a diagnostic:... https://github.com/m-labs/artiq/issues/835#issuecomment-333424828
<GitHub3> [artiq] whitequark commented on issue #407: @r-srinivas Can you please recheck using latest builds? https://github.com/m-labs/artiq/issues/407#issuecomment-333425043
<GitHub10> [artiq] whitequark commented on issue #407: @r-srinivas Can you please recheck using latest builds? We've done a lot of work making the networking side more robust. https://github.com/m-labs/artiq/issues/407#issuecomment-333425043
<GitHub134> [artiq] whitequark commented on issue #544: Stack probes were merged a good while ago in LLVM. There'll need to be some minimal work for OR1K for them to fully function. https://github.com/m-labs/artiq/issues/544#issuecomment-333425271
<GitHub176> [artiq] whitequark pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/7ad54e1dcfc905f4b50fcef9d68547bcacf4fe78
<GitHub176> artiq/master 7ad54e1 whitequark: firmware: unbreak heap view....
sb0 has joined #m-labs
<bb-m-labs> build #812 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/812
<GitHub109> [artiq] whitequark commented on issue #452: Triage: fixing this would be a research project that I don't think has a low enough cost/benefit ratio to undertake. https://github.com/m-labs/artiq/issues/452#issuecomment-333427321
<GitHub196> [artiq] whitequark closed issue #452: Incorrect error message when trying to access get_dataset in kernel https://github.com/m-labs/artiq/issues/452
<bb-m-labs> build #583 of artiq-win64-test is complete: Failure [failed conda_install] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/583 blamelist: whitequark <whitequark@whitequark.org>
<bb-m-labs> build #1702 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1702 blamelist: whitequark <whitequark@whitequark.org>
<bb-m-labs> build #813 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/813
<bb-m-labs> build #584 of artiq-win64-test is complete: Failure [failed conda_install] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/584 blamelist: whitequark <whitequark@whitequark.org>
<bb-m-labs> build #1703 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1703 blamelist: whitequark <whitequark@whitequark.org>
<GitHub100> [artiq] sbourdeauducq pushed 5 new commits to release-3: https://github.com/m-labs/artiq/compare/a49bb2bc50f3...db8300c99082
<GitHub100> artiq/release-3 67997d8 whitequark: compiler: correct semantics of integer % operator (#830).
<GitHub100> artiq/release-3 1521231 whitequark: compiler: correct semantics of floating point % operator (fix #830).
<GitHub100> artiq/release-3 a06f04d whitequark: compiler: minor intrinsic refactoring.
<GitHub7> [artiq] sbourdeauducq pushed 5 new commits to release-2: https://github.com/m-labs/artiq/compare/5c5f86cdea7a...8e3959d7ce1b
<GitHub7> artiq/release-2 8fd9ba9 whitequark: compiler: correct semantics of integer % operator (#830).
<GitHub7> artiq/release-2 05096a9 whitequark: compiler: correct semantics of floating point % operator (fix #830).
<GitHub7> artiq/release-2 d0276ab whitequark: compiler: minor intrinsic refactoring.
<sb0> bb-m-labs, force build --branch=release-2 artiq
<bb-m-labs> build #1704 forced
<bb-m-labs> I'll give a shout when the build finishes
<GitHub4> [artiq] sbourdeauducq pushed 1 new commit to release-3: https://github.com/m-labs/artiq/commit/45c6ca96f8466424144ec796914b5592e5fcc624
<GitHub4> artiq/release-3 45c6ca9 whitequark: firmware: unbreak heap view....
<bb-m-labs> build #814 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/814
<bb-m-labs> build #1704 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1704
<sb0> bb-m-labs, force build --branch=release-2 artiq
<bb-m-labs> build #1705 forced
<bb-m-labs> I'll give a shout when the build finishes
<GitHub34> [artiq] sbourdeauducq pushed 1 new commit to release-2: https://github.com/m-labs/artiq/commit/09822457a382877be54d2c10c4ba8601d1b298a5
<GitHub34> artiq/release-2 0982245 Sebastien Bourdeauducq: runtime: link libm in ksupport
<bb-m-labs> build #815 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/815
<GitHub55> [artiq] whitequark pushed 3 new commits to master: https://github.com/m-labs/artiq/compare/7ad54e1dcfc9...2684aec4c600
<GitHub55> artiq/master 2684aec whitequark: firmware: use read_unaligned instead of a hack. NFC.
<GitHub55> artiq/master fd07c3f whitequark: runtime: get rid of config_dummy.rs. NFC....
<GitHub55> artiq/master 73c76eb whitequark: firmware: eliminate most transmutes and document the rest. NFC.
<bb-m-labs> build #585 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/585
<bb-m-labs> build #1705 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1705
<GitHub105> [artiq] sbourdeauducq pushed 1 new commit to release-2: https://github.com/m-labs/artiq/commit/b84699873a28df55776eb1d842ac57a946bf39b9
<GitHub105> artiq/release-2 b846998 Sebastien Bourdeauducq: RELEASE_NOTES: 2.5
<GitHub178> [artiq] sbourdeauducq tagged 2.5 at a7b3c34: https://github.com/m-labs/artiq/commits/2.5
<sb0> bb-m-labs, force build --branch=release-2 artiq
<bb-m-labs> The build has been queued, I'll give a shout when it starts
<GitHub6> [artiq] sbourdeauducq pushed 1 new commit to release-3: https://github.com/m-labs/artiq/commit/a6cd42c4aa1d272f2181cb58624df021f44ebbd9
<GitHub6> artiq/release-3 a6cd42c Sebastien Bourdeauducq: RELEASE_NOTES: 2.5
<bb-m-labs> build #816 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/816
_whitelogger has joined #m-labs
<bb-m-labs> build #586 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/586
<bb-m-labs> build #1706 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1706
<bb-m-labs> build forced [ETA 35m47s]
<bb-m-labs> I'll give a shout when the build finishes
<GitHub86> [artiq] whitequark commented on issue #805: Updated testcase:... https://github.com/m-labs/artiq/issues/805#issuecomment-333439277
<GitHub73> [artiq] whitequark commented on issue #805: Unable to reproduce on latest master. All three variants underflow at 32 pulses. The LLVM IR also checks out. https://github.com/m-labs/artiq/issues/805#issuecomment-333439327
<GitHub34> [artiq] whitequark closed issue #805: kernel invariants: seconds to mu conversion not for free on kernel https://github.com/m-labs/artiq/issues/805
<GitHub114> [artiq] sbourdeauducq pushed 2 new commits to master: https://github.com/m-labs/artiq/compare/2684aec4c600...cda9719f4bbf
<GitHub114> artiq/master 84f2733 Sebastien Bourdeauducq: RELEASE_NOTES: 2.5
<GitHub114> artiq/master cda9719 Sebastien Bourdeauducq: gui: update version number in background
<GitHub13> [artiq] whitequark commented on issue #560: > I would do it the other way, in order to stay closer to Python semantics. Support optimized iteration on homogeneous tuples without unrolling, introduce a HeterogeneousCollection (or similarly named) type for the more special case of iterating (with unrolling) on disparate objects.... https://github.com/m-labs/artiq/issues/560#issuecomment-333439798
<sb0> bb-m-labs: force build --props=package=artiq-kc705-nist_qc2 --branch=release-2 artiq-board
<bb-m-labs> The build has been queued, I'll give a shout when it starts
<sb0> bb-m-labs: force build --props=package=artiq-pipistrello-nist_qc1 --branch=release-2 artiq-board
<bb-m-labs> The build has been queued, I'll give a shout when it starts
<GitHub112> [artiq] sbourdeauducq commented on issue #560: OK. https://github.com/m-labs/artiq/issues/560#issuecomment-333440599
<GitHub104> [artiq] sbourdeauducq commented on issue #560: OK, point taken. https://github.com/m-labs/artiq/issues/560#issuecomment-333440599
<bb-m-labs> build #817 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/817
<bb-m-labs> build forced [ETA 13m54s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #1707 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1707
<sb0> bb-m-labs: force build --props=package=artiq-kc705-nist_clock --branch=release-2 artiq-board
<bb-m-labs> The build has been queued, I'll give a shout when it starts
<bb-m-labs> build #818 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/818
<bb-m-labs> build forced [ETA 13m54s]
<bb-m-labs> I'll give a shout when the build finishes
<sb0> bb-m-labs: force build --props=package=artiq-kc705-nist_qc2 --branch=release-2 artiq-board
<bb-m-labs> The build has been queued, I'll give a shout when it starts
<sb0> bb-m-labs: force build --props=package=artiq-pipistrello-nist_qc1 --branch=release-2 artiq-board
<bb-m-labs> The build has been queued, I'll give a shout when it starts
<bb-m-labs> build #819 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/819
<bb-m-labs> build forced [ETA 12m05s]
<bb-m-labs> I'll give a shout when the build finishes
<GitHub153> [artiq] sbourdeauducq commented on issue #835: Python has some mechanism for turning in-place mutation into the other form automatically:... https://github.com/m-labs/artiq/issues/835#issuecomment-333442463
<GitHub170> [artiq] whitequark commented on issue #835: That's not the issue here. The real reason __iadd__ is not supported is that:... https://github.com/m-labs/artiq/issues/835#issuecomment-333445009
<GitHub59> [artiq] whitequark reopened issue #835: Compiler crash on list addition https://github.com/m-labs/artiq/issues/835
<GitHub194> [artiq] whitequark commented on issue #835: Actually, now that I think about it, the check should only apply to lists. And we have another bug elsewhere. https://github.com/m-labs/artiq/issues/835#issuecomment-333445137
<sb0> whitequark, how serious is that new bug?
<whitequark> sb0: I misremembered how we work with slices
<whitequark> no new bug
sb0 has quit [Quit: Leaving]
<bb-m-labs> build #820 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/820
<bb-m-labs> build #821 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/821
FabM has joined #m-labs
<bb-m-labs> build #587 of artiq-win64-test is complete: Warnings [warnings python_unittest] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/587 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<bb-m-labs> build #1708 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1708
<GitHub138> [artiq] whitequark pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/ca254ec55e49d73e8a9026d76b4d5c7af3af5a6e
<GitHub24> [artiq] whitequark closed issue #835: Compiler crash on list addition https://github.com/m-labs/artiq/issues/835
<GitHub138> artiq/master ca254ec whitequark: compiler: disallow op= on mutable lists only (fix #835)....
<bb-m-labs> build #1709 of artiq is complete: Failure [failed lit_test] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1709 blamelist: whitequark <whitequark@whitequark.org>
<GitHub157> [smoltcp] whitequark commented on pull request #43 927158d: Do you think you could finish the renaming in this commit? I'd like to keep history bisectable, and generally clean. https://git.io/vdnQf
<GitHub46> [smoltcp] whitequark commented on pull request #43 927158d: I can imagine that a network card could handle ipv4 checksum but not ipv6, so perhaps split these off into udpv4 and tcpv4? https://git.io/vdnQe
<GitHub34> [smoltcp] whitequark commented on pull request #43 927158d: `ChecksumCapabilities`, for consistence. https://git.io/vdnQv
<GitHub25> [smoltcp] whitequark commented on pull request #43 927158d: Do you think you could fold this commit into previous ones? Same reasoning as before. https://git.io/vdnQU
<GitHub122> [smoltcp] whitequark commented on pull request #43 927158d: I think it's worth passing a `&ChecksumCapabilities` around because all of the parse/emit methods already know what kind of packet are they working with, not individual `Checksum` fields, since then the resulting code is easier to read. `header.emit(&mut ip_packet, checksum_caps)` plus `if checksum_caps.ipv4.tx() { ... }` vs `header.emit(&mut ip_packet, emit_checksum)` plus `emit_che
<GitHub78> [smoltcp] whitequark commented on pull request #43 927158d: What's the rationale here? https://git.io/vdnQT
bb-m-labs has quit [Ping timeout: 258 seconds]
sb0 has joined #m-labs
<sb0> hmm the buildbot computer crashed
<GitHub85> [smoltcp] steffengy commented on pull request #43 927158d: Ensuring the checksum field is surely zeroed in the resulting packet.... https://git.io/vdcvG
sb0 has quit [Quit: Leaving]
rohitksingh has quit [Read error: Connection reset by peer]
rohitksingh has joined #m-labs
rohitksingh has quit [Read error: Connection reset by peer]
rohitksingh has joined #m-labs
bb-m-labs has joined #m-labs
rohitksingh has quit [Read error: Connection reset by peer]
rohitksingh has joined #m-labs
rohitksingh has quit [Read error: Connection reset by peer]
rohitksingh has joined #m-labs
rohitksingh has quit [Read error: Connection reset by peer]
<_florent_> rjo: i'm testing sayma flash as you wanted
<_florent_> can you help me, i have that: https://hastebin.com/ujeritodeq.pas
<_florent_> maybe i'm doing something wrong
rohitksingh has joined #m-labs
<_florent_> rjo: please ping me when you are there so that we look at that together
<rjo> _florent_: ping.
<rjo> _florent_: i had the impression that sayma (or the ftdi chip, or the jtag router, or the mmc) sometimes gets into a weird state. could you try power cycling?
<rjo> and can you give me a lsusb?
<_florent_> rjo: i'm back, i do that
<_florent_> rjo: indeed it's now different
<_florent_> it's also different with or without sayma rtm, whithout rtm i get:
<_florent_> which seems to be similar to your result
<_florent_> rjo: done for you test? results are similar and second spi flash is also not working on my board?
<rjo> _florent_: half done. ;)
<rjo> _florent_: the test without rtm looks ok. confirms what i have seen. thanks.
<_florent_> rjo: ok, what else can i do for you?? :)
<rjo> _florent_: in tcl/board/sayma_amc.cfg, could you enable line 36 and test again with rtm?
<_florent_> ok
<rjo> _florent_: that's with the `source [find cpld/xilinx-xc7.cfg]` line activated?
<rjo> _florent_: i'd be surprised. that would look different as it has a whole pile of expected id numbers.
<rjo> _florent_: sayma_amc.cfg should look like this: https://hastebin.com/ugozizahoz.bash
<rjo> _florent_: and then your top level script that you pass to openocd should look like https://hastebin.com/ugozizahoz.bash
<_florent_> rjo: sorry i read 26 and not 36...
<GitHub150> [smoltcp] steffengy commented on issue #43: @whitequark ... https://git.io/vdcmQ
<rjo> _florent_: forgot one change: make that "pld load 1 bscan_spi_xcku040-sayma.bit"
<GitHub32> [smoltcp] jordens commented on issue #43: Out of curiosity: Does someone have data on how much this speeds things up? How much time is spent on checksums in smoltcp (excluding the higher non-smoltcp protocol layers)? https://git.io/vdc3E
<rjo> _florent_: that still says "loaded file bscan_spi_xcku040-sayma.bit to pld device 0 in 3s 937395us" the bitstream should go to device 1.
<_florent_> rjo: sorry, that was the same link... Here are the results: https://hastebin.com/tocatuyevu.pas
<rjo> _florent_: great. that's it for now. thanks a bunch.
<GitHub88> [sinara] jordens deleted 0.1rc1 at 12d34d7: https://github.com/m-labs/sinara/commit/12d34d7
sb0 has joined #m-labs
<sb0> hm, what happened to the buildbot?
<sb0> sshd segfaulted
<sb0> 164 days uptime, should I preventively reboot it?
<sb0> bb-m-labs: force build --props=package=artiq-kc705-nist_qc2 --branch=release-2 artiq-board
<bb-m-labs> build forced [ETA 13m47s]
<bb-m-labs> I'll give a shout when the build finishes
<rjo> sb0: fine by me (if it comes up again).
<sb0> it's been acting weird today, did you or whitequark run something that hogged the memory?
<sb0> one of the build failed because vivado crashed after it failed to allocate memory
<rjo> whitequark was playing with the buildbot. all i ever did in the last weeks was compile bitstreams.
<sb0> nothing in SMART...
<sb0> btw I have a SSD drive collecting dust, should I put it in?
<bb-m-labs> build #822 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/822
<GitHub169> [smoltcp] podhrmic opened pull request #46: Fix ICMP Destination Unreachable packet causing panic (master...master) https://git.io/vdcD5
<whitequark> sb0: SSD drive, yes, absolutely, that would be a significant improvement
<whitequark> sb0: I'll reboot it in a bit
<whitequark> I upgraded the system
<whitequark> debian typically doesn't have issues like that but I suppose they fucked up something in glibc
stekern has quit [Read error: Connection reset by peer]
stekern has joined #m-labs
bb-m-labs has quit [Quit: buildmaster reconfigured: bot disconnecting]
bb-m-labs has joined #m-labs
<GitHub145> [smoltcp] whitequark commented on pull request #43 eae3799: Okay, this is worth a small comment in every call site. https://git.io/vdcpS
<GitHub156> [smoltcp] whitequark commented on pull request #43 eae3799: Same as below on rightwards drift. https://git.io/vdcje
<GitHub6> [smoltcp] whitequark commented on pull request #43 eae3799: `if checksum.udpv4.rx() && !packet.verify_checksum(src_addr, dst_addr)` avoids excessive rightwards drift. https://git.io/vdcjv
<GitHub130> [smoltcp] whitequark commented on pull request #43 eae3799: `checksum_caps` would be more clear. I actually got confused on the type of this variable while reviewing. https://git.io/vdcjf
<GitHub58> [smoltcp] steffengy commented on issue #43: @whitequark ... https://git.io/vdCvU
<GitHub90> [smoltcp] whitequark commented on pull request #43 29b1e39: Rebase issue? https://git.io/vdCIz
<GitHub64> [smoltcp] steffengy commented on pull request #43 9ec67cf: Oops. Fixed. https://git.io/vdCIy
<GitHub78> [smoltcp] whitequark commented on pull request #43 9ec67cf: Shouldn't we verify checksum in this method? Looks like I forgot to implement it. https://git.io/vdCIN
<GitHub82> [smoltcp] steffengy commented on pull request #43 9ec67cf: Yeah I'm not sure what the story is around there, that's what I meant with:... https://git.io/vdCLG
<GitHub195> [smoltcp] steffengy commented on issue #43: @whitequark And another round, thanks for the patience! https://git.io/vdCLp
<GitHub0> [smoltcp] whitequark closed pull request #43: hardware based checksum generation & validation (master...master) https://git.io/v55Ck
<GitHub63> [smoltcp] whitequark pushed 2 new commits to master: https://git.io/vdCcU
<GitHub63> smoltcp/master d5147ef Steffen Butzer: support hardware based checksum settings in during packet send/recv...
<GitHub63> smoltcp/master 9b1b0b4 Steffen Butzer: phy: introduce hardware based checksum settings, rename DeviceLimits...
<GitHub21> [smoltcp] whitequark closed issue #36: Hardware Checksum Calculation https://git.io/v5WRQ
<GitHub33> [smoltcp] whitequark commented on issue #43: Thanks! I'm looking forward to more great contributions from you. https://git.io/vdCcs
<travis-ci> m-labs/smoltcp#296 (master - d5147ef : Steffen Butzer): The build passed.
<travis-ci> batonius/smoltcp#94 (master - d5147ef : Steffen Butzer): The build passed.
<travis-ci> batonius/smoltcp#95 (default_route - 7b2cc2b : Egor Karavaev): The build passed.
<GitHub146> [artiq] r-srinivas commented on issue #407: Had a look at it using artiq 3.0 py_0+git04a9a0ce on Windows. The following experiment,... https://github.com/m-labs/artiq/issues/407#issuecomment-333680096
<GitHub18> [smoltcp] whitequark pushed 2 new commits to master: https://git.io/vdClS
<GitHub18> smoltcp/master 70248c5 whitequark: Formatting. NFC.
<GitHub18> smoltcp/master 58c12b8 whitequark: Reword checksum-related documentations....
<travis-ci> batonius/smoltcp#96 (master - 58c12b8 : whitequark): The build passed.
<travis-ci> batonius/smoltcp#97 (default_route - 253a14b : Egor Karavaev): The build passed.
<GitHub93> [smoltcp] batonius commented on issue #44: Rebased the branch.... https://git.io/vdC4W
<GitHub108> [smoltcp] whitequark commented on issue #44: Cool! https://git.io/vdCBw
<GitHub150> [smoltcp] whitequark pushed 1 new commit to master: https://git.io/vdCEI
<GitHub150> smoltcp/master c8ae7bd whitequark: Fix insufficient length validation in IPv4 packets....
<travis-ci> m-labs/smoltcp#300 (master - c8ae7bd : whitequark): The build passed.
<GitHub41> [smoltcp] whitequark commented on issue #46: I'm confused. What's the backtrace for the panic? https://git.io/vdCuy