Open Bug 877507 Opened 7 years ago Updated 2 years ago
We Fast Yet: Add padding when there is no more data from the build saves .
Today, I noticed that we were no longer checking performances on B2G since May 21st (*), previously the same happened between April 29th and May 7th. We noticed a huge regression when the build started again to check on May 7th, we should add a way to prevent such things by making these slave failures visible on awfy. One way to do it would be to shift the graph based on the current time. Another option would be to pad with fake (dashed) entries every 8 hours, such as we can fix them the next day without having too much false positive. (*) I noticed it because I was surprised that the screen still show the same result as the last time I noticed it running.
Product: Core → Testing
You need to log in before you can comment on or make changes to this bug.