3 ms·
99% chance it's just some calculation tool not truncating. I wouldn't be surprised if that text is machine generated from a template.
by fake-name 7y ago
99% chance it's just some calculation tool not truncating.
I wouldn't be surprised if that text is machine generated from a template.
- mike_hock 7y agoIt's obviously tool-generated. I think the question was, why does the tool show the non-truncated value for that one line, considering it put the truncated (%0.03f) version right next to it.
- JdeBP 7y agoHere's the repository. Look it up and tell us. * https://vote.debian.org/~secretary/devotee.git/ https://vote.debian.org/~secretary/devotee.git/
- mike_hock 7y agoWhat do you want me to tell you? dvt-rslt:367-368 the ratio is interpolated into the string output without any format specification (resulting in the full decimal expansion), whereas in the passing case (line 382) it is not. The ratio is formatted with %6.3f in both cases (369-372, 384-387). That's what it does. Doesn't tell us why (though it looks like a simple oversight on the programmer's part).
- nemetroid 7y agoJust for fun, I had a look. The commit which adds the non-truncated print changed some behaviour with regard to < vs <=, so it might have been added for debugging purposes and simply never removed.