[Insight-developers] Proposal to filter robot build results by git commit hash

[Cory Quammen]

I have a proposal for changing which results from robot builds are
filtered in CDash: filter by git commit hash.

Currently in gerrit, when you click the link for the robot builds for
a given gerrit patch set in a change, what you see are all the builds
for the change after 12 midnight the date they were submitted. If
several patch sets are pushed for that change on the same day, all the
builds from all patch sets show up in these filtered results.
Determining which build goes with which patch set can be difficult
because not all build machines take the same amount of time to build
and run the tests (I'm looking at you, Windows machine), so simply
looking at the build time does not necessarily tell you which patch
set it is from. If there is a lot of activity on a gerrit change, test
failures from previous patch sets may be interleaved with test
successes from the most recent patch, which makes reviewing more
difficult.

Now, it *is* possible to unambiguously determine which build is for
which patch set by clicking on the link to the updated files in CDash,
finding the Revision (git commit hash), then going back to gerrit and
matching this git commit hash with the patch number. However, this is
rather cumbersome for determining which build results go with which
patch sets. It would be a lot nicer if clicking on the link to CDash
would present a page with only the builds for that patch set.

It doesn't seem that CDash lets you filter by revision (at least it is
not exposed in the UI). Perhaps the first part of the git hash could
be appended after the topic name in the CDash build name.

Thanks for your consideration,
Cory

-- 
Cory Quammen
Research Associate
Department of Computer Science
University of North Carolina at Chapel Hill
http://www.cs.unc.edu/~cquammen