[Cdash] Duplicate build entries with CDash 2.0
peter at colberg.org
Thu Feb 9 15:37:15 UTC 2012
On Thu, Feb 09, 2012 at 09:00:02AM -0500, David Cole wrote:
> On Wed, Feb 8, 2012 at 9:30 PM, Peter Colberg <peter at colberg.org> wrote:
> > It turns out revision 2935 causes the duplicated build entries:
> > daa7f7b89f31b248d172b05237e2b6dc1052b4c3 is the first bad commit
> > commit daa7f7b89f31b248d172b05237e2b6dc1052b4c3
> > Author: david.cole <david.cole at 91079597-3006-4846-9bd3-4f3fb3d139a7>
> > Date: Tue Aug 2 21:43:38 2011 +0000
> > ENH: Include updates from related builds (those with the same stamp,
> > siteid and name) not just the one given buildid. When a subproject-based
> > dashboard submits its cycle of subproject builds, all after a single
> > ctest_start call, also typically followed by a single ctest_update call,
> > and then a loop of subproject configure/build/test sequences, we want the
> > updates gathered at the beginning to be reported for each subproject build
> > in non-collapsed viewing mode... This commit achieves that by introducing
> > the get_updates_buildid_clause function, and then using it everywhere the
> > buildupdate and updatefile tables are queried for update related
> > information.
> > git-svn-id: https://www.kitware.com/svn/CDash/trunk@293591079597-3006-4846-9bd3-4f3fb3d139a7
> Ugh. Looks like it started with one of my commits for better subproject
> Related builds are those with the same stamp, site and name, and yes, they
> should all be associated with the same project.
> You have duplicate rows appearing in your results, right? (Two buildid 1's
> on the first project's page, and two buildid 2's on the second project's
> page) -- only build id's associated with project 1 actually appear on
> project 1's page. Or am I misunderstanding?
That's correct, two id=1's on first project, two id=2's on second project.
More information about the CDash