Sequential IDs are important for LNT and llvmlab bisection tool.
LNT uses the “order” to capture the measured software changes. LNT does make
the assumption that orders are unique, so if a ID was the same on two branches,
LNT would assume that is the same change. If you never want to compare d
On 8 July 2016 at 01:56, Chris Matthews wrote:
> With both llvmlab and LNT, once you get to a range of IDs, it is needs to be
> easy to find out what commits or commit range those IDs map to. When given
> regression between 123 and 225, I need the list of commits, and I don’t want
> to log grep f