<d_n|a>
bb-m-labs: force build --branch=pull/1299/head artiq
<bb-m-labs>
build #2978 forced
<bb-m-labs>
I'll give a shout when the build finishes
<d_n|a>
whitequark: See PRs 1299/1300 regarding the escape analysis issue discussed earlier, and a (seemingly) obvious improvement in quoting tuples. I'll merge once green unless you have any objections.
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
_whitelogger has joined #m-labs
futarisIRCcloud has joined #m-labs
rohitksingh has quit [Ping timeout: 245 seconds]
rohitksingh has joined #m-labs
_whitelogger has joined #m-labs
rohitksingh has quit [Ping timeout: 255 seconds]
rohitksingh has joined #m-labs
_whitelogger has joined #m-labs
rohitksingh has quit [Ping timeout: 246 seconds]
rohitksingh has joined #m-labs
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
mumptai has joined #m-labs
<d_n|a>
bb-m-labs: force build --branch=pull/1300/head artiq
<bb-m-labs>
build #2979 forced
<bb-m-labs>
I'll give a shout when the build finishes
<d_n|a>
sb0: Any idea what's going on with the above set_log_level buildbot failures? The ping step succeeds, and locally a firmware build with the changes appears functional
<d_n|a>
Also, it looks like the lit tests are somehow pulling in an old build of the compiler; that error is precisely what the PR fixes (tests pass locally)
<d_n|a>
Reason tells me that it's probably a bug in the code, but I'm quite tempted to push those commits to master and take it from there...
sb0 has joined #m-labs
<sb0>
d_n|a: I don't know about set_log_level, but problems like the lit tests pulling an older version (and many other similar issues) is why we are using nix and hydra now
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
<d_n|a>
(I've just double-checked to be sure, and the lit tests indeed pass locally on master. The error in 2982 is exactly what I get if I revert the compiler sources.)
<sb0>
yeah it's just conda crap, the test passes on hydra