02:20 <sb0> whitequark, what's the conclusion for https://github.com/m-labs/artiq/issues/407 ?

02:27 <sb0> cr1901_modern, did you investigate the python asyncio OSError problem?

04:12 <whitequark> as of yet, nothing

07:20 <Sb0000> whitequark: well, 4-second compilation time for such simple code doesn't look good

07:21 <whitequark> I will go to the lab later today and measure dead time difference between linux and windows specifically, but otherwise...

07:22 <whitequark> 1) most of it is spent in LLVM 2) the solution for this is not making compilation faster, it's avoiding compilation whatsoever

07:22 <Sb0000> how come LLVM spends so much time compiling this?

07:22 <Sb0000> it compiles more complex code faster

07:23 <whitequark> the stats from my machine are not representative as it uses Debug LLVM

07:23 <whitequark> actually, let me look at conda

07:23 <whitequark> OH

07:23 <whitequark> oh shit

07:23 <whitequark> I think I know what happened

07:23 <whitequark> and why it's slow on Windows

07:24 <whitequark> ah. no. wrong guess. we build LLVM on Windows as Release, and do it properly

07:24 <whitequark> even without assertions

07:28 <whitequark> sb0000: does that lab perhaps have just a very slow PC on top of all that?

07:28 <whitequark> so far I haven't been able to reproduce the difference between Windows and Linux on the same hardware specifically

07:48 <Sb0000> whitequark: maybe, ask Raghu. it may also be loaded with "security" bloatware as Robert mentioned

07:48 <whitequark> ok, will do

07:50 <Sb0000> can you look at Rust after that?

07:50 <whitequark> ok

08:45 <cr1901_modern> sb0: No, I'll investigate today; I've seen OSError in the context of connecting sockets on Windows in my own code, but I didn't really expect it to appear during a version upgrade.

11:25 <whitequark> sb0: TTLs don't work.

11:26 <whitequark> or at least I cannot capture any signals on scope from any pins on the backplane, while outputting pulses to ttls 0-7

11:35 <whitequark> hm, not even sma_gpio works, wtf?

11:49 <whitequark> ...

11:49 <whitequark> I left the scope in "average" mode and forgot about it

12:32 <whitequark> sb0: ok, I've confirmed my earlier thoughts

12:32 <whitequark> will look at Rust

16:32 <GitHub89> [artiq] whitequark pushed 1 new commit to release-1: https://git.io/vKnze

16:32 <GitHub89> artiq/release-1 b5901db whitequark: compiler.testbench.perf_embedding: update for core changes.

17:55 <GitHub28> [artiq] whitequark pushed 1 new commit to release-1: https://git.io/vKnXi

17:55 <GitHub28> artiq/release-1 eceafad whitequark: compiler.testbench.perf_embedding: more fine grained reporting.

17:55 <GitHub150> [artiq] whitequark pushed 1 new commit to master: https://git.io/vKnXP

17:55 <GitHub150> artiq/master c5ba44b whitequark: compiler.testbench.perf_embedding: more fine grained reporting.

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

18:18 <bb-m-labs> build #256 of artiq-win64-test is complete: Failure [failed python_unittest] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/256 blamelist: whitequark <whitequark@whitequark.org>

18:18 <bb-m-labs> build #810 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/810 blamelist: whitequark <whitequark@whitequark.org>

19:22 <GitHub75> [artiq] jordens pushed 1 new commit to release-1: https://git.io/vKnAh

19:22 <GitHub75> artiq/release-1 078a9ab Sebastien Bourdeauducq: rtio: do not reset DDS and SPI PHYs on RTIO reset (#503)

20:29 <rjo> sb0, whitequark: do you guys have anything else pending for 1.2?