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
<GitHub91> [artiq] dhslichter opened pull request #231: Merge pull request #2 from m-labs/master (master...master) https://github.com/m-labs/artiq/pull/231
<GitHub37> [artiq] dhslichter closed pull request #231: Merge pull request #2 from m-labs/master (master...master) https://github.com/m-labs/artiq/pull/231
<GitHub1> [artiq] dhslichter reopened pull request #231: Merge pull request #2 from m-labs/master (master...master) https://github.com/m-labs/artiq/pull/231
<sb0> whitequark, host_only has broken the unittests
<whitequark> hm, thought I had fixed that
<GitHub141> [artiq] whitequark pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/e6185e16d80ba558bcc2e0dedf4da61b6a354226
<GitHub141> artiq/master e6185e1 whitequark: Commit missing parts of 127b117.
<GitHub57> [artiq] dhslichter closed pull request #231: Merge pull request #2 from m-labs/master (master...master) https://github.com/m-labs/artiq/pull/231
sb0 has quit [Quit: Leaving]
<rjo> whitequark: your memoize() is broken: it never updates the cache.
<whitequark> rjo: I wrote a memoize() ?
<whitequark> oh, in the debug info generator. fun.
<rjo> there is lru_cache somewhere in the stdlib
<bb-m-labs> build #108 of artiq is complete: Failure [failed python_unittest] Build details are at http://m-labs-buildserver.lan/buildbot/builders/artiq/builds/108 blamelist: whitequark <whitequark@whitequark.org>
sb0__ has joined #m-labs
<sb0__> whitequark: now there is this "hardware exception" bug ...
<sb0__> the new compiler has a lot of issues.
<whitequark> sure. it's much more complex.
<sb0__> happens all the time now
<whitequark> do you have a small repro?
<sb0__> and that's seriously annoying, every demo i have attempted has crashed
<whitequark> sb0__: hang on
<whitequark> was that after my sret fix?
<sb0__> yes
<whitequark> hm, very strange
<sb0__> before that it only crashed with small values of nrep
<whitequark> can you give me any of the crashing demos?
<sb0__> whitequark: in the issue. default_std.py
<sb0__> in conjunction with the std_include above
<sb0__> the crashing bit seems to be the assingment into self.counts
<sb0__> out-of-bounds error?
<whitequark> arrays are not copied on assignment
<sb0__> I'm talking about self.counts[self.rep_i] = cts
<sb0__> commenting this out makes the hardware exception disappear
<whitequark> oh
<whitequark> no, the EA is too low
<whitequark> exception 6 is unaligned access.
<sb0__> i guess it didn't crash there before the sret fix, because count() never returned and this was not executed
<sb0__> bugs, bugs, bugs, bugs ...
<sb0__> when will this end?
<whitequark> mhm, we need a more representative testsuite for the core device. beyond the basic operations
<whitequark> e.g. the portability testsuite found a lot of bugs... we don't have anything like that for RTIO though
<rjo> sure there is.
<whitequark> if it didn't catch this bug, it's not representative enough
<whitequark> I'll take a look at expanding it...
<rjo> artiq/test/coredevice/rtio.py
<whitequark> yes, I know
<sb0__> guess this test has not been run in a while, during which it broke.
<whitequark> mhm, yes, we should run those in the lab
<whitequark> actually, what's holding that off? it should be trivial to implement
<sb0__> whitequark: any ideas about this hw exception? it's blocking right now and i haven't found a small repro
<whitequark> let me finish fixing the compile error in GUI and I will minimize it
<whitequark> almost done
<sb0__> whitequark: attribute writeback of lists also looks broken ....
<sb0__> oh yes it is
<sb0__> meh
<whitequark> sigh
<GitHub75> [artiq] whitequark pushed 3 new commits to master: https://github.com/m-labs/artiq/compare/e6185e16d80b...67d2e7a82880
<GitHub75> artiq/master 8522278 whitequark: transforms.llvm_ir_generator: fix memoize().
<GitHub75> artiq/master 95470a5 whitequark: gui.log: work around a Qt layout bug.
<GitHub75> artiq/master 67d2e7a whitequark: worker: display compile warnings and errors nicely (#227).
<whitequark> sb0__: while I work on that crash, can you check if I really worked around that Qt bug?
<whitequark> sb0__: worker.py:184 leads to exceptions being formatted in really awful ways
<GitHub23> [artiq] whitequark pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/d3371215fb86b3f058de2a2f1997c60bfaa5ae57
<GitHub23> artiq/master d337121 whitequark: worker: make parent errors readable in log.
<GitHub72> [artiq] whitequark force-pushed master from d337121 to 6bf48e6: https://github.com/m-labs/artiq/commits/master
<GitHub72> artiq/master 6bf48e6 whitequark: worker: make parent errors readable in log.
<whitequark> wtf
<whitequark> now I just get
<whitequark> ERROR:master:artiq.master.scheduler:got worker exception in run stage, deleting RID 3
<whitequark> so now it's my turn to complain about bugs. without running artiq_master as -vv, the DEBUG messages don't appear in the GUI at all
<whitequark> therefore defeating the purpose of that log level switch
<whitequark> why do you print an exception as debug anyway?..
<whitequark> wtf is expid?
<sb0__> whitequark: the worker debug messages do appear in the gui, without master -vv.
<whitequark> no, they do not.
<whitequark> I had to do
<whitequark> - logger.debug("worker exception details", exc_info=True)
<whitequark> + logger.info("worker exception details", exc_info=True)
<whitequark> and actually not even that worked
<whitequark> logger.warn is the lowest level which makes them appear in the GUI
<sb0__> is the master calling that or the worker?
<whitequark> that's in master/scheduler.py
<sb0__> ok. so yes, that is dependent on the master debug level.
<GitHub68> [artiq] whitequark pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/13e65c2a0a75320d3b595df36ea20144ed8366c7
<GitHub68> artiq/master 13e65c2 whitequark: scheduler: make sure worker exceptions are not unexpectedly hidden.
<sb0__> unless you are debugging the master, you shouldn't have to touch it though
<whitequark> well, it crashed and I spent a lot of time figuring out why
<whitequark> hm, I cannot even copy log entries...
<whitequark> ValueError: cannot create an OBJECT array from memory buffer
<whitequark> wtf?
<whitequark> it tries to decode some worker pyon
<whitequark> sb0__: ok, I am unable to reproduce the bug on the lab kc705
<whitequark> the experiment just runs forever
<whitequark> oh, that's because it doesn't actually run
<whitequark> everything about artiq_master is so broken.
<whitequark> ah, no, not artiq_master's fault, my fault.
<whitequark> ok, I turned off simulation, but it still doesn't crash
<whitequark> nreps is set to 5...
<whitequark> sb0__: attribute writeback of lists works
<whitequark> testcase: http://hastebin.com/ucivohuzid.py
<whitequark> if you tried to do this...
<whitequark> then it's a bug in the sense that you shouldn't be allowed to do this.
<sb0__> yes, i did #2. what is the problem with that?
<whitequark> the allocated list only lives until the function returns
<whitequark> so of course you read back garbage
<sb0__> oh, so that might be why the experiment crashes too
<whitequark> ah, yes, most certainly.
<sb0__> since the list is allocated in rep_start
<whitequark> sb0__: try list[:] = [0 for ...]
<whitequark> yep, that works, but you need to write it as list[0:] because of some other bug
<whitequark> let me fix that one, it's easy
<rjo> sb0__: /joe beer any time?
<GitHub21> [artiq] whitequark pushed 2 new commits to master: https://github.com/m-labs/artiq/compare/13e65c2a0a75...cc228376275f
<GitHub21> artiq/master be560db whitequark: Commit missing parts of 13e65c2a.
<GitHub21> artiq/master cc22837 whitequark: transforms.inferencer: infer a monomorphic type for slice ":"
bb-m-labs has quit [Quit: buildmaster reconfigured: bot disconnecting]
<GitHub81> [buildbot-config] whitequark pushed 1 new commit to master: https://github.com/m-labs/buildbot-config/commit/05ddef6f433ab3466970cc475f05a1e8ec3fc2c3
<GitHub81> buildbot-config/master 05ddef6 whitequark: Merge build requests.
bb-m-labs has joined #m-labs
rohitksingh has joined #m-labs
sb0__ has quit [Quit: Page closed]
evilspirit has joined #m-labs
sb0 has joined #m-labs
ylamarre has quit [Quit: ylamarre]
stekern has quit [Ping timeout: 265 seconds]
rohitksingh has quit [Quit: Leaving.]
evilspirit has quit [Ping timeout: 264 seconds]
imrehg has joined #m-labs
attie has quit [Ping timeout: 260 seconds]
attie has joined #m-labs
attie has quit [Ping timeout: 246 seconds]
attie has joined #m-labs
attie has quit [Ping timeout: 264 seconds]
attie has joined #m-labs
imrehg has quit [Quit: Leaving]
sb0 has quit [Quit: Leaving]
bb-m-labs has quit [Quit: buildmaster reconfigured: bot disconnecting]
bb-m-labs has joined #m-labs
<bb-m-labs> build #116 of artiq is complete: Exception [exception deploy_doc] Build details are at http://m-labs-buildserver.lan/buildbot/builders/artiq/builds/116
bb-m-labs has quit [Client Quit]
bb-m-labs has joined #m-labs
<bb-m-labs> build #117 of artiq is complete: Exception [exception deploy_doc] Build details are at http://m-labs-buildserver.lan/buildbot/builders/artiq/builds/117
bb-m-labs has quit [Quit: buildmaster reconfigured: bot disconnecting]
bb-m-labs has joined #m-labs
<bb-m-labs> build #118 of artiq is complete: Exception [exception deploy_doc] Build details are at http://m-labs-buildserver.lan/buildbot/builders/artiq/builds/118
bb-m-labs has quit [Client Quit]
bb-m-labs has joined #m-labs
<bb-m-labs> build #119 of artiq is complete: Exception [exception deploy_doc] Build details are at http://m-labs-buildserver.lan/buildbot/builders/artiq/builds/119
bb-m-labs has quit [Quit: buildmaster reconfigured: bot disconnecting]
bb-m-labs has joined #m-labs
<bb-m-labs> build #120 of artiq is complete: Exception [exception deploy_doc] Build details are at http://m-labs-buildserver.lan/buildbot/builders/artiq/builds/120
bb-m-labs has quit [Client Quit]
bb-m-labs has joined #m-labs
<bb-m-labs> build #121 of artiq is complete: Exception [exception deploy_doc] Build details are at http://m-labs-buildserver.lan/buildbot/builders/artiq/builds/121
bb-m-labs has quit [Client Quit]
bb-m-labs has joined #m-labs
<bb-m-labs> build #122 of artiq is complete: Exception [exception deploy_doc] Build details are at http://m-labs-buildserver.lan/buildbot/builders/artiq/builds/122
bb-m-labs has quit [Client Quit]
bb-m-labs has joined #m-labs
<bb-m-labs> build #123 of artiq is complete: Exception [exception deploy_doc] Build details are at http://m-labs-buildserver.lan/buildbot/builders/artiq/builds/123
bb-m-labs has quit [Client Quit]
bb-m-labs has joined #m-labs
<bb-m-labs> build #124 of artiq is complete: Exception [exception deploy_doc] Build details are at http://m-labs-buildserver.lan/buildbot/builders/artiq/builds/124
<whitequark> fucking hell
<whitequark> pysftp is a piece of crap that doesn't actually implement sftp semantics
<whitequark> or... any usable semantics at all
<whitequark> doesn't even have rm_r
<whitequark> and of course its directory traverse code is completely unsuitable for implementing rm_r
bb-m-labs has quit [Quit: buildmaster reconfigured: bot disconnecting]
bb-m-labs has joined #m-labs
<bb-m-labs> build #125 of artiq is complete: Success [build successful] Build details are at http://m-labs-buildserver.lan/buildbot/builders/artiq/builds/125
<whitequark> amazing
<whitequark> I can't believe it finally worked. only took me a dozen tries.
<GitHub104> [buildbot-config] whitequark pushed 1 new commit to master: https://github.com/m-labs/buildbot-config/commit/d1c43a45b42615837f8535888f2ed45906245dbd
<GitHub104> buildbot-config/master d1c43a4 whitequark: Upload ARTIQ manual via SFTP.
evilspirit has joined #m-labs
<GitHub174> [artiq] whitequark pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/785b2736a0eee15f9bf22540f72f11a52c076ab2
<GitHub174> artiq/master 785b273 whitequark: Document core device cache (#219).
bb-m-labs has quit [Quit: buildmaster reconfigured: bot disconnecting]
bb-m-labs has joined #m-labs
<whitequark> so, it didn't actually work. crap.
evilspirit has quit [Ping timeout: 264 seconds]
bb-m-labs has quit [Quit: buildmaster reconfigured: bot disconnecting]
bb-m-labs has joined #m-labs
stekern has joined #m-labs
mumptai has joined #m-labs
<whitequark> ok, much better now
stekern has quit [Ping timeout: 272 seconds]
sb0 has joined #m-labs
sb0 has quit [Client Quit]
sb0 has joined #m-labs
<sb0> whitequark, er, master no longer starts... looking into it
<sb0> ah, it's my fault.
<GitHub85> [artiq] sbourdeauducq pushed 2 new commits to master: https://github.com/m-labs/artiq/compare/785b2736a0ee...f9323c328621
<GitHub85> artiq/master a808d26 Sebastien Bourdeauducq: style
<GitHub85> artiq/master f9323c3 Sebastien Bourdeauducq: master/worker_db/get_last_rid: ignore improperly named files
sb0 has quit [Quit: Leaving]
rohitksingh has joined #m-labs
<cr1901_modern> rjo: Adding onto what you said re: xc3sprog and OpenOCD proxies being different, I did a quick lookup. It appears that the xc3sprog proxies write to a block RAM using the SPI protocol. The block RAM attaches itself to the boundary scan implemenation on the FPGA, and is manipulated through the block RAM. So yea, it is indeed much more complicated :P
rohitksingh has quit [Quit: Leaving.]
<rjo> cr1901_modern: i explained all this to uwe bonnes and he said he would look into making xc3sprog use the trivial (openocd) bitstreams.