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
_whitelogger has joined #m-labs
Ultrasauce has joined #m-labs
Ultrasauce has quit [Ping timeout: 246 seconds]
sb0 has joined #m-labs
<sb0> and possibly the new rust i2c code is also broken
<sb0> the i2c failure was less visible before as the core device crashed from the dds test
<GitHub101> [artiq] sbourdeauducq pushed 2 new commits to master: https://git.io/v1Wqb
<GitHub101> artiq/master 3520038 Sebastien Bourdeauducq: manual: precisions about TTL sampling
<GitHub101> artiq/master 617f689 Sebastien Bourdeauducq: runtime: more concise message
<bb-m-labs> build #243 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/243
<bb-m-labs> build #1139 of artiq is complete: Failure [failed python_unittest_1] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1139 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
sb0 has quit [Ping timeout: 244 seconds]
sb0 has joined #m-labs
mumptai_ has joined #m-labs
mumptai has quit [Ping timeout: 244 seconds]
Zou has joined #m-labs
Gurty has quit [Ping timeout: 256 seconds]
sandeepkr has joined #m-labs
rohitksingh has joined #m-labs
rohitksingh has quit [Client Quit]
<whitequark> rjo: will look into it a bit later today
sb0 has quit [Remote host closed the connection]
FabM has quit [Quit: ChatZilla 0.9.93 [Firefox 45.5.0/20161115214506]]
<whitequark> sb0: doubt about i2c code. i've definitely verified that tests passed, and they also passed prior to dds changes.
<whitequark> will look into it anyway
<whitequark> rjo: ok. hm. this approach is not entirely valid.
<whitequark> let's see if it's salvageable
sb0 has joined #m-labs
sandeepkr has quit [Ping timeout: 256 seconds]
sandeepkr has joined #m-labs
<sb0> whitequark, so what's the plan for fixing the core device hangs?
<sb0> they released lwip 2.0.0 on Nov 10
<sb0> have you tried it?
<sb0> there seems to be a bunch of changes
Zou has quit [Quit: Kooll ~o~ datalove <3³\infty]
Gurty has joined #m-labs
<sb0> we're not using a release right now
<whitequark> sb0: I'll try that first and if it doesn't work, try migrating to a different stack
<whitequark> I've spent some time trying to debug it and it's not promising
<whitequark> went over the way I use its API again and I don't see any issues...
<sb0> what's your concern with it exactly, and what makes you think another stack won't also have the bug content of a rain forest?
<sb0> I mean, looking at the lwip code, I don't find obvious evidence of sloppy programming
<whitequark> sb0: looking at how it works, I do
<GitHub190> [artiq] sbourdeauducq pushed 1 new commit to drtio: https://git.io/v1WuG
<GitHub190> artiq/drtio 4b97b9f Sebastien Bourdeauducq: drtio: add clock constraints
<GitHub111> [artiq] sbourdeauducq pushed 1 new commit to drtio: https://git.io/v1Wgl
<GitHub111> artiq/drtio 5d145ff Sebastien Bourdeauducq: drtio: add false paths between sys and transceiver clocks
sandeepkr has quit [Ping timeout: 265 seconds]