Go to https://treeherder.mozilla.org/#/jobs?repo=mozilla-aurora&revision=9a294e361e63 for example. The top change listed in the push is a06ac8e3220a. Now click on the "and more" link to see the pushlog on hg.m.o, this will take you to https://hg.mozilla.org/releases/mozilla-aurora/pushloghtml?changeset=a06ac8e3220a which shows that the top commit in the push was actually 8849dd1a4a79. Why does TH show a bunch of commits from the middle of the push?
Even worse is if you load more changesets on the TH page, the topmost commit on the next push is 8849dd1a4a79. It's like TH took one giant push (8849dd1a4a79) and listed it twice, but the second time only listed half of it, and listed them in the wrong order. Or something.
Treeherder had some ingestion issues with pushes with many hundreds of commits, like what happens when m-c merges to aurora or when aurora merges to beta, etc. I think this managed to get fixed by something in the last month or two, as the most recent merge from m-c to aurora managed to be displayed in a single push: https://treeherder.mozilla.org/#/jobs?repo=mozilla-aurora&revision=0d6a91c76a9eddf2219caf028dea130f2d683ec2
I agree with Wes that this should be fixed now. We have done a lot of data ingestion fixes in this area in the last month. But we should keep an eye on this to see if it happens again. If so, then let's investigate it at that time.
Haven't heard anything in the last five months. Can we close this?
Wes: yeah, let's close it. We'll reopen if we see it again. :)
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.