TE-msmith: the underlying issue is that 2844 is showing you the header+body, whereas verification is checking what's shown in the body. From line 2111 + line 2815 those two are different things. That's whats crazy
TE-msmith
that doesn't compute
because when I ran it just now, it worked fine
that's what that gist I linked is
hamiltont
Look at the travis output you posted, but look at line 2110 instead of line 2844
Ok, then I'll try to freshen up local environment and commit fix
TE-msmith
ah
xt
My changes are merged upstreamed now, though, so fork not needed
(I think)
thanks for helping me, TE-msmith
TE-msmith
sure thing
let me know when you commit again and I'll try pulling and testing again
xt
will do!
TE-msmith
travis is being... unrtrustworthy
xt
they renamed stdmacro fail! 5 days ago "steveklabnik. cgaebel: fail! is now panic! as of last night"
hehe..shows you how usntable that language is
hamiltont
oh good lord
#include <stdio-nope-can't-touch-this.h>
acidx
the nice thing about rust is that code written in it don't even have time to get rusty. :)
TE-msmith
>_<
so, one of those questions is "why do you hate me, travis?"
hamiltont
oh man, the dstat output alex-techempower coded up is insanely cool once I figured out how to plot it
You can see so many metrics about how a framewrok perormed during test run
With a hardware profile of things like max network bytes available, this could probably be used to quantify how much each resource is consumed during a framework run - would be great for quantitatively identifying which resource is the bottleneck
TE-msmith
mmmyeah
I know some of those words
hamiltont
ha ha :-P
It's enough data to make any sysadmin cry with happiness?
TE-msmith
so... yay?
sounds like yay
dear wt, why does it honestly take 20m to build you?
hamiltont
Very yay - just needs to be visualized and then have some code searching for common patterns