rohitksingh_work has quit [Ping timeout: 244 seconds]
rohitksingh_work has joined #m-labs
esden has quit [Read error: Connection reset by peer]
esden has joined #m-labs
m4ssi has joined #m-labs
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
<rjo>
sb0: was artiq on windows tested with the new build bot?
sb0 has joined #m-labs
rohitksingh_wor1 has joined #m-labs
rohitksingh_work has quit [Ping timeout: 258 seconds]
rohitksingh_wor1 has quit [Quit: Leaving.]
d_n|a has joined #m-labs
d_n|a_ has quit [Ping timeout: 255 seconds]
<sb0>
rjo: sure, it still runs the tests in the windows vm
<sb0>
well, a new VM that gets snapshotted so that conda can't fuck it up permanently
<rjo>
sb0: is the install from conda script being tested and does the dashboard start after that?
<rjo>
*install-with-conda
<sb0>
I tested it manually (note that the previous buildbot did not test that either) and it worked
<sb0>
and that script is unsuitable for CI because it exercises highly non-deterministic parts of conda
<sb0>
accesses anaconda.org etc.
sb0 has quit [Quit: Leaving]
sb0 has joined #m-labs
<sb0>
rjo: I have an idea
<sb0>
afaik the conda installer doesn't touch the registry or anything
<sb0>
so, we could zip the whole conda folder with conda, artiq and its dependencies installed it it, distribute that, and offer as an installation option
<sb0>
this will also speed things up because "conda install" is slow
<sb0>
it's also reproducible and does not involve anaconda.org