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
sb0 has joined #m-labs
<sb0> cr1901_modern, i have not tried it
sb0 has quit [Quit: Leaving]
froggytoad has joined #m-labs
early has joined #m-labs
early` has quit [Quit: Leaving]
sb0 has joined #m-labs
sandeepkr has quit [Ping timeout: 240 seconds]
sandeepkr has joined #m-labs
mumptai has joined #m-labs
sandeepkr_ has joined #m-labs
sandeepkr has quit [Ping timeout: 240 seconds]
sandeepkr_ has quit [Ping timeout: 240 seconds]
sandeepkr has joined #m-labs
FabM has joined #m-labs
mumptai has quit [Remote host closed the connection]
kuldeep has joined #m-labs
kuldeep has quit [Max SendQ exceeded]
sandeepkr has quit [Ping timeout: 260 seconds]
<GitHub60> [smoltcp] whitequark pushed 1 new commit to master: https://git.io/vM5C1
<GitHub60> smoltcp/master bb630e1 whitequark: Reset the TCP retransmit timer on valid ACK if transmit half is open.
<travis-ci> m-labs/smoltcp#46 (master - bb630e1 : whitequark): The build passed.
<whitequark> rjo: is there a python test runner yet that's not an utter atrocity or do I have to *also* write that?
<whitequark> seriously. there are three different invocations I have to use depending on whether I'm running a module, a class or a function
<rjo> whitequark: pytest? (-runner)
<whitequark> hm
<whitequark> that crashes on ARTIQ tests with an internal error
<rjo> file a bug. we might be messing with some test internals.
<whitequark> on ARTIQ?
<whitequark> I don't *think* we mess with internals, but sure...
<GitHub120> [artiq] whitequark opened issue #657: pytest fails with ARTIQ tests https://git.io/vM58i
sandeepkr has joined #m-labs
<rjo> whitequark: i meant on pytest. they shouldn't have internal errors.
<whitequark> oh
<whitequark> actually, nevermind.
<whitequark> pytest is *even worse* than unittest with regards to my complaint: https://github.com/pytest-dev/pytest/issues/2193
<whitequark> 'baroque and foreign'
<GitHub8> [artiq] whitequark closed issue #657: pytest fails with ARTIQ tests https://git.io/vM58i
<GitHub63> [smoltcp] whitequark pushed 1 new commit to master: https://git.io/vM54D
<GitHub63> smoltcp/master d57b42c whitequark: Don't send TCP FIN flag yet if next segment will also have data.
<travis-ci> m-labs/smoltcp#47 (master - d57b42c : whitequark): The build passed.
<whitequark> 1, 2, 5, 6 are fixed
<whitequark> there's a new issue with test_args
<GitHub118> [artiq] jordens opened issue #658: pipistrello runtime does not compile [PPP] https://git.io/vM50g
<whitequark> ah, no, it's a stream desync issue
<GitHub38> [artiq] whitequark force-pushed smoltcp from bb0b8c8 to 42cae20: https://git.io/vMoWb
<GitHub38> artiq/smoltcp 6a7d014 whitequark: firmware: remove false dependency from runtime to ksupport....
<GitHub38> artiq/smoltcp fc60e73 whitequark: firmware: integrate smoltcp instead of lwip.
<GitHub38> artiq/smoltcp 8471c5f whitequark: firmware: increase post-boot UART speed to 921600.
<whitequark> aha, that wasn't actually a smoltcp bug
<whitequark> sb0: down to three failures, test_i2c_switch, test_clock_generator_loopback and test_pulse_rate_dds
<whitequark> none of them caused by smoltcp
<whitequark> I'm merging.
<GitHub120> [artiq] whitequark pushed 5 new commits to master: https://git.io/vM5Mu
<GitHub120> artiq/master 0253e0a whitequark: firmware: remove false dependency from runtime to ksupport....
<GitHub120> artiq/master 971e4c3 whitequark: firmware: increase post-boot UART speed to 921600.
<GitHub120> artiq/master 13a544e whitequark: artiq_devtool: add boot+log action; avoid forwarder crashes.
<bb-m-labs> build #320 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/320
<bb-m-labs> build #1224 of artiq is complete: Failure [failed python_unittest_1] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1224 blamelist: whitequark <whitequark@whitequark.org>
<whitequark> hrm. what?
<whitequark> sb0: after merge the runtime no longer boots
<whitequark> I've no idea what did you change
<whitequark> hang on
<whitequark> scratch that. it does boot. just... not on the buildserver?
<whitequark> bb-m-labs: force build artiq
<bb-m-labs> build forced [ETA 46m31s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #321 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/321
sandeepkr has quit [Ping timeout: 255 seconds]
<bb-m-labs> build #1225 of artiq is complete: Failure [failed python_unittest_1] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1225
sandeepkr has joined #m-labs
kuldeep has joined #m-labs
sb0 has quit [Ping timeout: 240 seconds]
sb0 has joined #m-labs
* whitequark stares
<whitequark> what the heck
<GitHub189> [smoltcp] whitequark pushed 1 new commit to master: https://git.io/vMd3A
<GitHub189> smoltcp/master 778add2 whitequark: Update dev-dependencies.
<GitHub112> [smoltcp] whitequark pushed 1 new commit to master: https://git.io/vMdsv
<GitHub112> smoltcp/master 2fedc76 whitequark: Bump to 0.2.0.
<travis-ci> m-labs/smoltcp#48 (master - 778add2 : whitequark): The build passed.
<travis-ci> m-labs/smoltcp#49 (master - 2fedc76 : whitequark): The build passed.
mumptai has joined #m-labs
sb0 has quit [Quit: Leaving]
sandeepkr has quit [Ping timeout: 240 seconds]
kuldeep has quit [Ping timeout: 255 seconds]
<whitequark> oh
<whitequark> it crashes, but *only* when the unittests are ran from the m-labs server
<whitequark> ah. got a trace for that. fix incoming...
_rht has joined #m-labs
kuldeep has joined #m-labs
<GitHub20> [smoltcp] whitequark pushed 1 new commit to master: https://git.io/vMFI2
<GitHub20> smoltcp/master b90495f whitequark: Correctly treat TCP ACKs that acknowledge both data and a FIN.
mumptai has quit [Quit: Verlassend]
<travis-ci> m-labs/smoltcp#50 (master - b90495f : whitequark): The build passed.
<GitHub163> [artiq] whitequark pushed 1 new commit to master: https://git.io/vMFqa
<GitHub163> artiq/master 4d05c70 whitequark: firmware: update smoltcp.
<bb-m-labs> build #322 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/322
_rht has quit [Quit: Connection closed for inactivity]
<bb-m-labs> build #1226 of artiq is complete: Failure [failed python_unittest_1] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1226 blamelist: whitequark <whitequark@whitequark.org>