02:06 <sb0> whitequark, are you working on the TCP bug?

02:06 <sb0> rjo, ok thanks

06:37 <GitHub93> [artiq] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/5d63489080e49b9a3e81c4c085ff1dd29905fa74

06:37 <GitHub93> artiq/master 5d63489 Sebastien Bourdeauducq: i2c,spi: add busno error detection

07:01 <bb-m-labs> build #629 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/629

07:05 <bb-m-labs> build #1564 of artiq is complete: Failure [failed python_unittest_2] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1564 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>

07:32 <GitHub120> [artiq] sbourdeauducq pushed 3 new commits to master: https://github.com/m-labs/artiq/compare/5d63489080e4...09d198c7a103

07:32 <GitHub120> artiq/master 09d198c Sebastien Bourdeauducq: test: add test for exception on non-existent I2C bus

07:32 <GitHub120> artiq/master d08bd58 Sebastien Bourdeauducq: versioneer: cut git hashes consistently (#753)

07:32 <GitHub120> artiq/master 6c6bb67 Sebastien Bourdeauducq: libboard: fix compiler warning on not(has_i2c)

07:58 <bb-m-labs> build #630 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/630

08:02 <bb-m-labs> build #1565 of artiq is complete: Failure [failed python_unittest_2] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1565 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>

08:50 <GitHub123> [artiq] sbourdeauducq closed issue #753: version mismatch error due to string length mismatch https://github.com/m-labs/artiq/issues/753

08:50 <GitHub23> [artiq] sbourdeauducq commented on issue #753: fixed https://github.com/m-labs/artiq/issues/753#issuecomment-309378101

11:04 <whitequark> sb0: yes

13:08 <rjo> bb-m-labs: force build --props=package=artiq-kc705-phaser artiq-board

13:08 <bb-m-labs> build forced [ETA 14m58s]

13:08 <bb-m-labs> I'll give a shout when the build finishes

13:34 <bb-m-labs> build #631 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/631

14:16 <GitHub193> [artiq] jbqubit commented on issue #752: @jordens What's the status on this? https://github.com/m-labs/artiq/issues/752#issuecomment-309453183

14:37 <GitHub115> [artiq] jordens commented on issue #752: Joe, the status is waiting. Quote from above:... https://github.com/m-labs/artiq/issues/752#issuecomment-309459419

14:57 <rjo> sb0, whitequark: is the kc705-aux/ad9154-fmc-ebz/rigol scope still connected? if not, could you wire it?

15:12 <GitHub11> [artiq] jbqubit commented on issue #752: I see. I tested and posted screen shots for ... https://github.com/m-labs/artiq/issues/752#issuecomment-309470627

15:15 <GitHub45> [artiq] jordens commented on issue #752: Thanks. Testing the current version fine.... https://github.com/m-labs/artiq/issues/752#issuecomment-309471608

15:17 <GitHub91> [artiq] jbqubit commented on issue #751: observation: sawg.reset() breaks swag... https://github.com/m-labs/artiq/issues/751#issuecomment-309472238

15:17 <sb0> rjo, it is still connected

15:18 <sb0> is it not working?

15:19 <GitHub50> [artiq] jbqubit commented on issue #752: This is not using sawgx.reset(). See #751.... https://github.com/m-labs/artiq/issues/752#issuecomment-309472948

15:23 <GitHub158> [artiq] jordens opened issue #756: sawg.reset() broken https://github.com/m-labs/artiq/issues/756

15:32 <rjo> sb0: scope not up it seems.

15:34 <whitequark> rjo: not in HK right now

15:35 <sb0> rjo, I'll check it tomorrow

15:35 <rjo> sb0, whitequark: thanks.

15:35 <sb0> but last time I had a look it was on

15:35 <sb0> so it may be a problem with the network cable?

15:36 <sb0> I assume you've used the power cycler...

15:37 <rjo> sb0: yep. .132 is down and the name doesn't resolve.

15:38 <sb0> have you nmapped the IP range? there should be only the scope, router, printer and PC right now

15:40 <rjo> nothing.

15:45 <GitHub178> [artiq] sbourdeauducq pushed 3 new commits to master: https://github.com/m-labs/artiq/compare/09d198c7a103...8f2d85fc5b2d

15:45 <GitHub178> artiq/master 8f2d85f Sebastien Bourdeauducq: add back ad9154_reg.py

15:45 <GitHub178> artiq/master c86029b Sebastien Bourdeauducq: i2c: expose restart as syscall, add structure for I2C-over-DRTIO

15:45 <GitHub178> artiq/master 268b7d8 Sebastien Bourdeauducq: typo

15:46 <GitHub197> [artiq] sbourdeauducq pushed 1 new commit to release-2: https://github.com/m-labs/artiq/commit/2383ea748f9dbfd294bf55c3681b3eb2434fb8d4

15:46 <GitHub197> artiq/release-2 2383ea7 Sebastien Bourdeauducq: versioneer: cut git hashes consistently (#753)

15:51 <GitHub189> [artiq] sbourdeauducq commented on issue #740: The files in f3c7a7de3be9a89a14b2d5e5540affd0393d4591, except ``test_ad9154_status.py`` that can be reintroduced as-is, do other manipulations to the JESD core that are a bit annoying to support over DRTIO. What about moving them to firmware? Perhaps those tests could be run at each boot. https://github.com/m-labs/artiq/issues/740#issuecomment-309482449

15:55 <GitHub103> [artiq] jordens commented on issue #740: Running them at Sayma boot is good. Depending on the clocking we might have to delay that though. https://github.com/m-labs/artiq/issues/740#issuecomment-309483863

15:57 <GitHub26> [artiq] sbourdeauducq commented on issue #740: The satellite manager should be capable of bringing up all the clocking by itself. https://github.com/m-labs/artiq/issues/740#issuecomment-309484542

16:06 <GitHub129> [artiq] jordens opened issue #757: phaser spi problem https://github.com/m-labs/artiq/issues/757

16:06 <rjo> sb0: ^^ afaict this came since the last couple commits.

16:07 <rjo> sb0: i'll rebuild with current master.

16:14 <sb0> it would be nice to have spi unittests

16:14 <GitHub13> [artiq] jordens commented on issue #752: Thanks. Testing the current version is fine.... https://github.com/m-labs/artiq/issues/752#issuecomment-309471608

16:24 <bb-m-labs> build #632 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/632 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>

16:24 <bb-m-labs> build #1566 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1566 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>

16:26 <rjo> sb0: HITL?

16:28 <sb0> yes

16:30 <sb0> maybe a sd card can be used as victim

16:31 <sb0> on the kc705

16:32 <rjo> yep. the dac board doesn't have miso unfortunately.

16:33 <sb0> ? so how does ad9154_test_status work?

16:37 <rjo> the ams101 dac board for the kc705, not the ad9154

16:40 <GitHub133> [artiq] jordens commented on issue #757: can't reproduce with `3.0.dev+1141.g8f2d85fc` https://github.com/m-labs/artiq/issues/757#issuecomment-309496809

16:40 <GitHub194> [artiq] jordens closed issue #757: phaser spi problem https://github.com/m-labs/artiq/issues/757

16:47 <sb0> rjo, spi looks flaky. I sometimes get the correct prodid 0x9154 for the DAC, and sometimes 0x-6eac

16:50 <sb0> rjo, that's by repeatedly running the new test_ad9154_status that I just committed

16:50 <GitHub112> [artiq] sbourdeauducq pushed 5 new commits to master: https://github.com/m-labs/artiq/compare/8f2d85fc5b2d...c74de6ae969b

16:50 <GitHub112> artiq/master 39ddb66 Sebastien Bourdeauducq: phaser: add AD9154 SPI access driver to example ddb

16:50 <GitHub112> artiq/master 470bce6 Sebastien Bourdeauducq: coredevice: add AD9154 SPI access driver

16:50 <GitHub112> artiq/master a6d0682 Sebastien Bourdeauducq: fix indentation

16:50 <sb0> the temp_code also looks weird

16:55 <sb0> hm, temp_code stabilized around 22k eventually

16:57 <sb0> it's only the first spi read that sometimes breaks, reading prodid the second time works fine

17:09 <rjo> sb0: we have been both using that board in the last couple of hours.

17:10 <rjo> sb0: i don't remember seeing SPI issues. might be a new thing.

17:14 <bb-m-labs> build #633 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/633

17:19 <bb-m-labs> build #1567 of artiq is complete: Failure [failed python_unittest_2] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1567 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>

21:32 <travis-ci> batonius/smoltcp#1 (packet_dispatch - b2aba01 : Egor Karavaev): The build failed.

21:32 <travis-ci> Change view : https://github.com/batonius/smoltcp/commit/b2aba01fe0ab

21:32 <travis-ci> Build details : https://travis-ci.org/batonius/smoltcp/builds/244701026

23:20 <GitHub185> [artiq] jbqubit commented on issue #752: I tested again this afternoon. The output still includes enormous harmonics. Can you reproduce on your hardware? ... https://github.com/m-labs/artiq/issues/752#issuecomment-309600089