Suspicious time diff at https://perf.rust-lang.org/status.html in took/expected #1713
Comments
|
cranelift is already back to 3 mins
|
|
Yeph, in first message there second table, where it can be seen:
|
|
Both runs was try runs, so possible difference in try/post-merge runs can't be here. |
|
The second table still has the estimate at 9m50s, while I'm saying the estimate is now fixed. Some try runs may have been slow and I also indeed would like to know whether we use them for the time estimates: it seems possible if we're actually using the "last run", but I don't know for sure. We'll see when jakub is back from vacation. |
|
Looking at digits,
We can try to check source code to dig possible truth :-) |
|
It's my recollection that we're using the last run but wasn't sure if try builds were used or not -- and as you say it seems like they are ^^ |
|
Yeah, it's always estimated from the most recent run. We should probably ignore try runs though, I'll look into it. |
This probably shouldn't be fixed until reason why this difference shows up will be found. Or maybe didn't changed at all, with current behavior we can at least saw difference and start digging; without that - noone will catch this. |
Time displayed at https://perf.rust-lang.org/status.html for took/expected heavily differs for some runs, while perf result shows no difference.
For example, for run rust-lang/rust#115388 (comment)
Notice cranelift, cargo, derive time diff for took/expected, while results clean https://perf.rust-lang.org/compare.html?start=b1b244da6527cf2ba36e88d02275f4c64a0c90d8&end=24259321f2e7a82959b47b86ded3d1073f281746&stat=instructions:u
And next perf for 6ff94474e1d11 (rust-lang/rust#115391 (comment)) run bounces back:
Quite sus number diff, while nothing interesting can be seen in perf results.
The text was updated successfully, but these errors were encountered: