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
larsc has quit [Ping timeout: 245 seconds]
larsc has joined #m-labs
_whitelogger has joined #m-labs
rohitksingh_work has joined #m-labs
<GitHub> [pythonparser] whitequark closed pull request #16: pythonparser.compat_ast as a tested drop-in replacement of stdlib ast (master...compat_ast) https://github.com/m-labs/pythonparser/pull/16
<GitHub> [pythonparser] whitequark pushed 1 new commit to master: https://github.com/m-labs/pythonparser/commit/6872c8f66e86b13acb4620f0e2bd496aa93060e5
<GitHub> pythonparser/master 6872c8f whitequark: Add a statement at EOF lexer test.
<GitHub> [pythonparser] whitequark tagged 1.1 at master: https://github.com/m-labs/pythonparser/commits/1.1
<GitHub> [conda-recipes] whitequark pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/f2ae1388e7486f0970c5a7ef11b9981ffe7f852b
<GitHub> conda-recipes/master f2ae138 whitequark: pythonparser: bump to 1.1.
<whitequark> bb-m-labs: force build --props=package=pythonparser conda-lin64
<bb-m-labs> build forced [ETA 30 seconds]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #319 of conda-lin64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/319
<GitHub156> [artiq] whitequark pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/53f7d145a428db92d7e0a0fb4e35572de61e342f
<GitHub156> artiq/master 53f7d14 whitequark: conda: update pythonparser dependency.
<whitequark> sb0: rjo: should be fixed.
<whitequark> I haven't realized non-conda users would use pythonparser from pip, or that the published version had a bug related to bytes...
<bb-m-labs> build #1549 of artiq is complete: Failure [failed conda_install_local] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1549 blamelist: whitequark <whitequark@whitequark.org>
<GitHub2> [artiq] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/ed2b27fed28ad327af767848d2c1fc9193524172
<GitHub2> artiq/master ed2b27f Sebastien Bourdeauducq: conda: fix pythonparser dependency
<bb-m-labs> build #606 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/606
<bb-m-labs> build #1550 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1550 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<sb0> jbqubit, as for your "crc failed" error, load the runtime with flterm for now.
<sb0> until this new yak is shaved
ohsix has quit [Ping timeout: 246 seconds]
cr1901_modern has quit [Read error: Connection reset by peer]
sb0 has quit [Quit: Leaving]
ohsix has joined #m-labs
sb0 has joined #m-labs
rohitksingh_work has quit [Read error: Connection reset by peer]
rohitksingh_work has joined #m-labs
<rjo> bb-m-labs: force build --props=package=artiq-kc705-phaser artiq-board
<bb-m-labs> build forced [ETA 14m53s]
<bb-m-labs> I'll give a shout when the build finishes
<GitHub164> [artiq] jordens pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/fecc42fd0c49c3b3735e67aacd35fd18fb7e5709
<GitHub164> artiq/master fecc42f Robert Jordens: sawg/phaser: expand documentation (closes #750)
<GitHub40> [artiq] jordens closed issue #750: sawg: phaser documentation https://github.com/m-labs/artiq/issues/750
<bb-m-labs> build #607 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/607
<rjo> bb-m-labs: force build --props=package=artiq-kc705-phaser artiq-board
<bb-m-labs> The build has been queued, I'll give a shout when it starts
<bb-m-labs> build #608 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/608 blamelist: Robert Jordens <rj@m-labs.hk>
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build forced [ETA 14m53s]
<bb-m-labs> build #1551 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1551 blamelist: Robert Jordens <rj@m-labs.hk>
<bb-m-labs> build #609 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/609
<rjo> whitequark, sb0: ^^ any idea?
<whitequark> no idea but I vaguely recall something similar...
rohitksingh_wor1 has joined #m-labs
rohitksingh_work has quit [Ping timeout: 240 seconds]
rohitksingh_wor1 has quit [Read error: Connection reset by peer]
jbqubit_ has joined #m-labs
<jbqubit_> rjo: is build successful yet? I'd like to test #473
jbqubit_ has quit [Client Quit]
jbqubit__ has joined #m-labs
jbqubit__ has quit [Client Quit]
jbqubit__ has joined #m-labs
jbqubit__ has quit [Client Quit]
<rjo> bb-m-labs: force build --props=package=artiq-kc705-phaser artiq-board
<bb-m-labs> build forced [ETA 14m53s]
<bb-m-labs> I'll give a shout when the build finishes
<rjo> sb0, whitequark: do you manage versions (e.g. for conda-build) on the build slaves manually?
<bb-m-labs> build #610 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/610
<GitHub92> [artiq] jbqubit commented on issue #750: Regarding https://github.com/m-labs/artiq/commit/fecc42fd0c49c3b3735e67aacd35fd18fb7e5709 . Thank you for the additional docs. ... https://github.com/m-labs/artiq/issues/750#issuecomment-308425283
<whitequark> rjo: yes
<whitequark> that was before i learned ansible
<rjo> whitequark: ok. how can we fix the buildbot? in the long term everybody just fiddling and bolting onto it won't really work.
<whitequark> rjo: fix as in have a single source of authority?
<rjo> whitequark: currently fix it so it builds bitstreams again. but in the long term we need to at least track what we do and why we did it and what issues we solved how.
<whitequark> I have no idea how to fix this failure, the last time sb0 twiddled it somehow I think
<whitequark> in the long term, sure, I can set up ansible
<whitequark> it's a tire fire alright, but it's a significantly smaller tire fire than chef or puppet, and only moderately revolting
jbqubit_ has joined #m-labs
jbqubit_ has quit [Ping timeout: 260 seconds]
jbqubit__ has joined #m-labs
jbqubit__ has quit [Client Quit]
<sb0> this problem existed before I touched it, it's been happening sporadically for many months
<sb0> and yes, this kind of buildbot non-determinism is obnoxious
sb0 has quit [Quit: Leaving]
<whitequark> it's just the usual conda garbage, no?
<whitequark> if you want me to rollback the VM before every build, no problem, I can do that almost trivially
jbqubit_ has joined #m-labs
sb0 has joined #m-labs
<sb0> VM rollback does sound like a good idea
<sb0> or just reset the conda stuff
<sb0> I think there are parts that are not built in a VM?
sb0 has quit [Quit: Leaving]
sb0 has joined #m-labs
sb0 has quit [Quit: Leaving]
sb0 has joined #m-labs
rohitksingh has joined #m-labs
sb0 has quit [Quit: Leaving]
sb0 has joined #m-labs
rohitksingh has quit [Quit: Leaving.]
<whitequark> I don't think so?
<whitequark> I'm not sure but I don't think so
<whitequark> oh, hang on
<whitequark> ARTIQ is not built in a VM, we use VMs only for the rest of the conda packages
<whitequark> ameliorating this requires an incredibly annoying dance with USB forwarding every time we're flashing something
<whitequark> I'm not ready to debug that
<whitequark> (we need the dance because kc705 is used both from the host VM and the one-off build VM...)
<whitequark> (I mean host OS)
<sb0> anyway right now the priority should be the TCP bug and other 3.0 issues
<whitequark> ok...
cr1901_modern has joined #m-labs
<GitHub177> [smoltcp] batonius opened pull request #15: Factor out the "raw_socket" and "tap_interface" features (master...split_std) https://git.io/vHF2d
jbqubit_ has quit [Ping timeout: 260 seconds]