01:38 <GitHub59> [artiq] sbourdeauducq closed issue #642: HasEnvironment prepare method https://git.io/v19GN

01:38 <GitHub188> [artiq] sbourdeauducq commented on issue #642: ``HasEnvironment`` just provides access to the dataset, devices, etc. without the prepare/run/analyze structure that comes with ``Experiment`` and relates to the pipeline stages of the scheduler. So not in ARTIQ. But you can implement it yourself by copy-pasting this small bit of ARTIQ code where you define ``prepare`` (``self.children`` is provided by ``HasEnvironment``):... https://git.io/v1HTQ

10:04 <sb0> why does the runtime depend on kernel32-sys?

10:17 <whitequark> sb0: a historic sequence of events that i won't go into

10:17 <whitequark> this will stop being the case once byteorder 1.0 is released, which is soon

11:14 <GitHub136> [artiq] sbourdeauducq pushed 1 new commit to master: https://git.io/v1HXe

11:14 <GitHub136> artiq/master 9967dfc Sebastien Bourdeauducq: runtime: reorganize to support DRTIO satellite firmware

11:17 <sb0> whitequark, so we should move i2c into libbsp, and make it more generic so it can be run either on the kernel CPU or on a single-CPU system

11:17 <sb0> also this new i2c code doesn't work

11:21 <sb0> whitequark, how is the network code coming along?

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

11:57 <whitequark> sb0: how come it doesn't work? it passed tests

11:57 <whitequark> I specifically checked that it passes tests before committing...

11:57 <whitequark> but ok, I've already been going to check it

11:58 <whitequark> as for network, I just finished some more necessary refactoring, so now the application side of the stack works fine

11:58 <whitequark> I'll push it a bit later

11:58 <sb0> did it pass tests?

11:59 <whitequark> yes, it passed tests

11:59 <whitequark> you can check out the commit that added it if you don't believe me...

11:59 <sb0> http://buildbot.m-labs.hk/builders/artiq/builds/1162/steps/python_unittest_1/logs/stdio

11:59 <sb0> test_i2c_switch (artiq.test.coredevice.test_i2c.I2CTest) ... FAIL

12:00 <whitequark> ok, I understand that it fails

12:00 <whitequark> I will look into it

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

13:29 <GitHub29> [artiq] sbourdeauducq pushed 2 new commits to master: https://git.io/v1HdJ

13:29 <GitHub29> artiq/master 9a564e0 Sebastien Bourdeauducq: firmware: make libbsp a crate

13:29 <GitHub29> artiq/master c99388f Sebastien Bourdeauducq: firmware: use M-Labs as author in Cargo.toml files

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

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

16:56 <GitHub193> [artiq] jbqubit opened issue #643: phaser2 configure device using openocd https://git.io/v1QnI

17:28 <GitHub173> [artiq] jbqubit commented on issue #643: @jordens from your email I resolved the second two... https://git.io/v1QlQ

17:41 <GitHub115> [artiq] jordens closed issue #643: phaser2 configure device using openocd https://git.io/v1QnI

17:41 <GitHub155> [artiq] jordens commented on issue #643: There should be a `jtagspi_init 0 /path/to/bscan_spi_xc7k325t.bit` after the init.... https://git.io/v1Q4u

17:43 <GitHub3> [artiq] whitequark commented on issue #643: We can bring back test mode if there's enough interest, there's no fundamental reason for its removal. https://git.io/v1Q4o

18:37 <GitHub80> [artiq] jbqubit commented on issue #643: Ah, thanks Robert.... https://git.io/v1Q2T

18:46 <GitHub35> [artiq] jbqubit opened issue #644: test mode support via serial interface https://git.io/v1Qay

19:00 <GitHub91> [artiq] jbqubit opened issue #645: search feature broken in html manual https://git.io/v1QwA

19:06 <GitHub7> [artiq] jordens commented on issue #645: Works for me https://m-labs.hk/artiq/manual-release-2/search.html?q=pulse&check_keywords=yes&area=default https://git.io/v1Qr5

19:29 <GitHub158> [artiq] jbqubit commented on issue #645: Your search string "pulse" returns... https://git.io/v1QPv

21:34 <GitHub45> [artiq] jbqubit commented on issue #582: @jordens please reopen this. https://git.io/v1Qxb

21:46 <mithro> This is kind of a weird question, but is there a way to check an invariant in a simulation test? IE set something which is checked *every* clock cycle?