This is an old behavior. But I agree it's misleading. I think it's more of an UI issue. When Perfherder creates new alert summaries, it groups them based on repo, framework, current push & previous push (this is [the responsible code](https://github.com/mozilla/treeherder/blob/master/treeherder/perf/alerts.py#L106-L110)). Problem is the UI displays only the first 3 characteristics, but not the 4th one. Thus, the UI is *falsely* telling the users: "See this summary from repo X & framework Y? Well, it was caused by current push Z" when instead it should say "See this summary from repo X & framework Y? It was caused by this suspect patch, which consists of all changesets from previous push Z1 up to and including current push Z2".
Bug 1600004 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This is an old behavior. But I agree it's misleading. I think it's more of an UI issue. When Perfherder creates new alert summaries, it groups them based on **repository**, **framework**, **current push** & **previous push** (this is [the responsible code](https://github.com/mozilla/treeherder/blob/master/treeherder/perf/alerts.py#L106-L110)). Problem is the UI displays only the first 3 characteristics, but not the 4th one. Thus, the UI is *falsely* telling the users: "See this summary from repo X & framework Y? Well, it was caused by current push Z" when instead it should say "See this summary from repo X & framework Y? It was caused by this suspect patch, which consists of all changesets from previous push Z1 up to and including current push Z2".