From kristofer.tingdahl at dgbes.com Fri May 15 10:24:35 2015 From: kristofer.tingdahl at dgbes.com (Kristofer Tingdahl) Date: Fri, 15 May 2015 16:24:35 +0200 Subject: [Cdash] Problems e-mailing users about problems in builds Message-ID: Hi, I have a CI which is reporting into a dashboard, and I want my users to get an e-mail if they are causing a problem. The problem is that I cannot get it working. I have polluted cdash with add_log to understand what is happening. It turns out that the SQL query in NNN, for instance: SELECT author,email,committeremail FROM updatefile AS uf,build2update AS b2u WHERE b2u.updateid=uf.updateid AND b2u.buildid='65962' does never return anything. It turns out that the insert into the "build2update" that associates the buildid with the update id comes later, and at that point, no-one is checking if there should be e-mails sent. >From the ctest side, I see from the log that it alsways sends the Build first, followed by the Configure, and last the Update xml files. Since the insert into build2update comes at when the update is submitted, I tried to reverse the order by having ctest_sumbit (PART ... ), but then I get different build-numbers. Any ideas on how to proceed? - Kristofer -- *Dr. Kristofer Tingdahl**Chief Executive Officer* *______________________________* *dGB Earth Sciences*Phone:+31 53 4315155Skype:dgbtingdahlE-mail: kristofer.tingdahl at dgbes.comInternet:dgbes.com & opendtect.org *______________________________* -------------- next part -------------- An HTML attachment was scrubbed... URL: From clinton at elemtech.com Fri May 15 11:46:18 2015 From: clinton at elemtech.com (Clinton Stimpson) Date: Fri, 15 May 2015 09:46:18 -0600 Subject: [Cdash] Problems e-mailing users about problems in builds In-Reply-To: References: Message-ID: <1475860.oX9dvKgzdg@stryke> On Friday, May 15, 2015 04:24:35 PM Kristofer Tingdahl wrote: > Hi, > > I have a CI which is reporting into a dashboard, and I want my users to get > an e-mail if they are causing a problem. The problem is that I cannot get > it working. > > I have polluted cdash with add_log to understand what is happening. It > turns out that the SQL query in NNN, for instance: > > SELECT author,email,committeremail FROM updatefile AS uf,build2update AS > b2u WHERE b2u.updateid=uf.updateid AND b2u.buildid='65962' > > > does never return anything. It turns out that the insert into the > "build2update" that associates the buildid with the update id comes later, > and at that point, no-one is checking if there should be e-mails sent. > > > From the ctest side, I see from the log that it alsways sends the Build > first, followed by the Configure, and last the Update xml files. Since the > insert into build2update comes at when the update is submitted, I tried to > reverse the order by having ctest_sumbit (PART ... ), but then I get > different build-numbers. > > Any ideas on how to proceed? > You could first check to see if this covers your problem: https://public.kitware.com/Bug/view.php?id=15453 The debugging you are doing so far sounds much like the debugging I did a while back. Its a problem where users are subscribed to receive emails when their own commits cause problems. When users are subscribed to receive all emails, its not a problem. There is a link to a mailing list discussion about it as well. It has been resolved, and there is a fix posted on the mailing list. Which can be found here: https://github.com/Kitware/CDash/commit/d8d550e969173067d292db6e91bf9a0d9a4c6276 Clint From jgfouca at sandia.gov Fri May 15 15:40:49 2015 From: jgfouca at sandia.gov (Foucar, James G) Date: Fri, 15 May 2015 19:40:49 +0000 Subject: [Cdash] length of time item remains on dashboard Message-ID: Hello, My current project has a number of "Nightly" tests that run for several days. The issue I'm having is that these builds are posted to CDash and only remain on the Nightly dashboard for about 24 hours. I really love for the dashboard to display a build until a newer build with the same name is submitted. Is this possible? Thanks, -Jim -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Fri May 15 16:21:04 2015 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Fri, 15 May 2015 16:21:04 -0400 Subject: [Cdash] length of time item remains on dashboard In-Reply-To: References: Message-ID: On Fri, May 15, 2015 at 3:40 PM, Foucar, James G wrote: > Hello, > > My current project has a number of ?Nightly? tests that run for several > days. The issue I?m having is that these builds are posted to CDash and > only remain on the Nightly dashboard for about 24 hours. I really love for > the dashboard to display a build until a newer build with the same name is > submitted. Is this possible? > Not that I know of. As you noticed, CDash currently only supports reporting build results on a day to day basis. It would be nice if this behavior could be configured differently per build group: daily, weekly, last N builds, etc. As things are now, the only workaround I can think of would be to resubmit the same .xml files day after day. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgfouca at sandia.gov Fri May 15 17:31:47 2015 From: jgfouca at sandia.gov (Foucar, James G) Date: Fri, 15 May 2015 21:31:47 +0000 Subject: [Cdash] [EXTERNAL] Re: length of time item remains on dashboard In-Reply-To: References: Message-ID: Thanks, I may try that workaround. A related question: According to the Ctest documentation, CTEST_NIGHTLY_START_TIME defines the 24-hour window that a build will be displayed on the dashboard. We have a variety of tests on different machines starting at different times. My goal is to at least get builds on the dashboard for the full 24 hours, so for each build submission, I've defined the nightly start time as the current time. This doesn't appear to be working as I intended because I see some of my tests from last night have already been removed from the dashboard. It's like the CTEST_NIGHTLY_START_TIME being submitted for later builds is impacting all the builds. How does CDash manage the nightly start times? Is it global or per-build? Thanks, -Jim From: Zack Galbreath > Date: Friday, May 15, 2015 at 2:21 PM To: "Foucar, James G" > Cc: "cdash at public.kitware.com" > Subject: [EXTERNAL] Re: [Cdash] length of time item remains on dashboard On Fri, May 15, 2015 at 3:40 PM, Foucar, James G > wrote: Hello, My current project has a number of "Nightly" tests that run for several days. The issue I'm having is that these builds are posted to CDash and only remain on the Nightly dashboard for about 24 hours. I really love for the dashboard to display a build until a newer build with the same name is submitted. Is this possible? Not that I know of. As you noticed, CDash currently only supports reporting build results on a day to day basis. It would be nice if this behavior could be configured differently per build group: daily, weekly, last N builds, etc. As things are now, the only workaround I can think of would be to resubmit the same .xml files day after day. -------------- next part -------------- An HTML attachment was scrubbed... URL: From prwolfe at sandia.gov Fri May 15 21:37:08 2015 From: prwolfe at sandia.gov (Wolfenbarger, Paul R) Date: Sat, 16 May 2015 01:37:08 +0000 Subject: [Cdash] [EXTERNAL] Re: length of time item remains on dashboard In-Reply-To: References: Message-ID: In fact we do have a version of cdash that allows us to do daily or weekly reports. We would like it to be more general than it currently is. ---------------------------------------------------------------------------------------- "The one important thing I have learned over the years is the difference between taking one's work seriously and taking one's self seriously. The first is imperative and the second is disastrous." - Margot Fonteyn, prima ballerina Paul R. Wolfenbarger, P.E., M.S. Computational Simulation Infrastructure DevOps Product Owner Sandia National Laboratories P.O. Box 5800 MS 0845 Albuquerque, NM 87185-0845 505-844-5458 phone prwolfe at sandia.gov ---------------------------------------------------------------------------------------- From: Zack Galbreath > Date: Friday, May 15, 2015 at 2:21 PM To: "Foucar, James G" > Cc: "cdash at public.kitware.com" > Subject: [EXTERNAL] Re: [Cdash] length of time item remains on dashboard On Fri, May 15, 2015 at 3:40 PM, Foucar, James G > wrote: Hello, My current project has a number of "Nightly" tests that run for several days. The issue I'm having is that these builds are posted to CDash and only remain on the Nightly dashboard for about 24 hours. I really love for the dashboard to display a build until a newer build with the same name is submitted. Is this possible? Not that I know of. As you noticed, CDash currently only supports reporting build results on a day to day basis. It would be nice if this behavior could be configured differently per build group: daily, weekly, last N builds, etc. As things are now, the only workaround I can think of would be to resubmit the same .xml files day after day. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristofer.tingdahl at dgbes.com Mon May 18 03:40:08 2015 From: kristofer.tingdahl at dgbes.com (Kristofer Tingdahl) Date: Mon, 18 May 2015 09:40:08 +0200 Subject: [Cdash] Problems e-mailing users about problems in builds In-Reply-To: <1475860.oX9dvKgzdg@stryke> References: <1475860.oX9dvKgzdg@stryke> Message-ID: Dear Clint, thanks, this resolved it! Cheers, Kristofer On Fri, May 15, 2015 at 5:46 PM, Clinton Stimpson wrote: > On Friday, May 15, 2015 04:24:35 PM Kristofer Tingdahl wrote: > > Hi, > > > > I have a CI which is reporting into a dashboard, and I want my users to > get > > an e-mail if they are causing a problem. The problem is that I cannot get > > it working. > > > > I have polluted cdash with add_log to understand what is happening. It > > turns out that the SQL query in NNN, for instance: > > > > SELECT author,email,committeremail FROM updatefile AS uf,build2update AS > > b2u WHERE b2u.updateid=uf.updateid AND b2u.buildid='65962' > > > > > > does never return anything. It turns out that the insert into the > > "build2update" that associates the buildid with the update id comes > later, > > and at that point, no-one is checking if there should be e-mails sent. > > > > > > From the ctest side, I see from the log that it alsways sends the Build > > first, followed by the Configure, and last the Update xml files. Since > the > > insert into build2update comes at when the update is submitted, I tried > to > > reverse the order by having ctest_sumbit (PART ... ), but then I get > > different build-numbers. > > > > Any ideas on how to proceed? > > > > You could first check to see if this covers your problem: > https://public.kitware.com/Bug/view.php?id=15453 > > The debugging you are doing so far sounds much like the debugging I did a > while back. > > Its a problem where users are subscribed to receive emails when their own > commits cause problems. When users are subscribed to receive all emails, > its > not a problem. > > There is a link to a mailing list discussion about it as well. > > It has been resolved, and there is a fix posted on the mailing list. > Which can be found here: > > https://github.com/Kitware/CDash/commit/d8d550e969173067d292db6e91bf9a0d9a4c6276 > > Clint > > -- *Dr. Kristofer Tingdahl**Chief Executive Officer* *______________________________* *dGB Earth Sciences*Phone:+31 53 4315155Skype:dgbtingdahlE-mail: kristofer.tingdahl at dgbes.comInternet:dgbes.com & opendtect.org *______________________________* -------------- next part -------------- An HTML attachment was scrubbed... URL: From vodall at gmail.com Wed May 20 22:43:40 2015 From: vodall at gmail.com (Bill V) Date: Wed, 20 May 2015 19:43:40 -0700 Subject: [Cdash] External programs accessing CTest/CDash database Message-ID: Are there any sample projects available where the CTest database is accessed by scripts outside of the web interface for various data queries and extraction? We'd like to create a CSV file of build timings for reports other than what is currently available. The information to do it is in the CDash scripts but if there's some python or other code available it'll give a good start. I found https://github.com/soonhokong/cdash/blob/master/testSummary.php but that's another web ap. Thanks! Bill From zack.galbreath at kitware.com Thu May 21 09:42:36 2015 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Thu, 21 May 2015 09:42:36 -0400 Subject: [Cdash] External programs accessing CTest/CDash database In-Reply-To: References: Message-ID: On Wed, May 20, 2015 at 10:43 PM, Bill V wrote: > Are there any sample projects available where the CTest database is > accessed by scripts outside of the web interface for various data > queries and extraction? Here's an example Python script used by the VTK developers to more easily track down failing tests: https://github.com/Kitware/VTK/blob/master/Utilities/Maintenance/vtk_fail_summary.py In general, it is a goal of ours to make it easier to access the information in the CDash database. We've made some progress on this recently, but it will still be some time before this effort is complete. > We'd like to create a CSV file of build > timings for reports other than what is currently available. The > information to do it is in the CDash scripts but if there's some > python or other code available it'll give a good start. > Take a look at the documentation here: http://public.kitware.com/Wiki/CDash:API I'm not 100% sure, but the "revisionstatus" task might give you the information that you're seeking. -------------- next part -------------- An HTML attachment was scrubbed... URL: From DLRdave at aol.com Thu May 21 09:58:05 2015 From: DLRdave at aol.com (David Cole) Date: Thu, 21 May 2015 09:58:05 -0400 Subject: [Cdash] External programs accessing CTest/CDash database In-Reply-To: References: Message-ID: There are some python scripts in the VTK code base that pull/poll some data from CDash and report on certain test results. You could probably use that as a guide for figuring out how to do a few things. For example, these three: https://github.com/Kitware/VTK/blob/master/Utilities/Maintenance/vtk_fail_summary.py https://github.com/Kitware/VTK/blob/master/Utilities/Maintenance/vtk_site_history.py https://github.com/Kitware/VTK/blob/master/Utilities/Maintenance/vtk_submitter_summary.py HTH, David C. On Wed, May 20, 2015 at 10:43 PM, Bill V wrote: > Are there any sample projects available where the CTest database is > accessed by scripts outside of the web interface for various data > queries and extraction? We'd like to create a CSV file of build > timings for reports other than what is currently available. The > information to do it is in the CDash scripts but if there's some > python or other code available it'll give a good start. > > I found https://github.com/soonhokong/cdash/blob/master/testSummary.php > but that's another web ap. > > Thanks! > > Bill > _______________________________________________ > Cdash mailing list > Cdash at public.kitware.com > http://public.kitware.com/mailman/listinfo/cdash From kristofer.tingdahl at dgbes.com Thu May 21 10:40:22 2015 From: kristofer.tingdahl at dgbes.com (Kristofer Tingdahl) Date: Thu, 21 May 2015 16:40:22 +0200 Subject: [Cdash] E-mail on new errors, not existing Message-ID: Hi, In the our CDASH - CI implementation, it sometimes happens that a test fails (the world is not perfect - right). If developer A has written that, he will get an e-mail. If developer B commits a bit later a new revision that is completely unrelated to the one A did, it will also fail the test if A has not fixed his crap yet. The problem is that B will also get an e-mail about the failed test which was caused by A. I would wish to filter this a bit, so that B does only get an e-mail if there are NEW problems in the build, i.e. what you see with the +1 signs in the GUI. Is there a way to do that. It is clear that the system can figure out the +1,-1 data, so it should be in there. Any hints anyone? - K -- *Dr. Kristofer Tingdahl**Chief Executive Officer* *______________________________* *dGB Earth Sciences*Phone:+31 53 4315155Skype:dgbtingdahlE-mail: kristofer.tingdahl at dgbes.comInternet:dgbes.com & opendtect.org *______________________________* -------------- next part -------------- An HTML attachment was scrubbed... URL: From vodall at gmail.com Thu May 21 12:42:46 2015 From: vodall at gmail.com (Bill V) Date: Thu, 21 May 2015 09:42:46 -0700 Subject: [Cdash] External programs accessing CTest/CDash database In-Reply-To: References: Message-ID: > Here's an example Python script used by the VTK developers to more easily > track down failing tests: > > https://github.com/Kitware/VTK/blob/master/Utilities/Maintenance/vtk_fail_summary.py > > In general, it is a goal of ours to make it easier to access the information > in the CDash database. We've made some progress on this recently, but it > will still be some time before this effort is complete. Thank you folks - this looks like just what we need. Bill From kristofer.tingdahl at dgbes.com Fri May 15 14:24:35 2015 From: kristofer.tingdahl at dgbes.com (Kristofer Tingdahl) Date: Fri, 15 May 2015 16:24:35 +0200 Subject: [Cdash] Problems e-mailing users about problems in builds Message-ID: Hi, I have a CI which is reporting into a dashboard, and I want my users to get an e-mail if they are causing a problem. The problem is that I cannot get it working. I have polluted cdash with add_log to understand what is happening. It turns out that the SQL query in NNN, for instance: SELECT author,email,committeremail FROM updatefile AS uf,build2update AS b2u WHERE b2u.updateid=uf.updateid AND b2u.buildid='65962' does never return anything. It turns out that the insert into the "build2update" that associates the buildid with the update id comes later, and at that point, no-one is checking if there should be e-mails sent. >From the ctest side, I see from the log that it alsways sends the Build first, followed by the Configure, and last the Update xml files. Since the insert into build2update comes at when the update is submitted, I tried to reverse the order by having ctest_sumbit (PART ... ), but then I get different build-numbers. Any ideas on how to proceed? - Kristofer -- *Dr. Kristofer Tingdahl**Chief Executive Officer* *______________________________* *dGB Earth Sciences*Phone:+31 53 4315155Skype:dgbtingdahlE-mail: kristofer.tingdahl at dgbes.comInternet:dgbes.com & opendtect.org *______________________________* -------------- next part -------------- An HTML attachment was scrubbed... URL: From clinton at elemtech.com Fri May 15 15:46:18 2015 From: clinton at elemtech.com (Clinton Stimpson) Date: Fri, 15 May 2015 09:46:18 -0600 Subject: [Cdash] Problems e-mailing users about problems in builds In-Reply-To: References: Message-ID: <1475860.oX9dvKgzdg@stryke> On Friday, May 15, 2015 04:24:35 PM Kristofer Tingdahl wrote: > Hi, > > I have a CI which is reporting into a dashboard, and I want my users to get > an e-mail if they are causing a problem. The problem is that I cannot get > it working. > > I have polluted cdash with add_log to understand what is happening. It > turns out that the SQL query in NNN, for instance: > > SELECT author,email,committeremail FROM updatefile AS uf,build2update AS > b2u WHERE b2u.updateid=uf.updateid AND b2u.buildid='65962' > > > does never return anything. It turns out that the insert into the > "build2update" that associates the buildid with the update id comes later, > and at that point, no-one is checking if there should be e-mails sent. > > > From the ctest side, I see from the log that it alsways sends the Build > first, followed by the Configure, and last the Update xml files. Since the > insert into build2update comes at when the update is submitted, I tried to > reverse the order by having ctest_sumbit (PART ... ), but then I get > different build-numbers. > > Any ideas on how to proceed? > You could first check to see if this covers your problem: https://public.kitware.com/Bug/view.php?id=15453 The debugging you are doing so far sounds much like the debugging I did a while back. Its a problem where users are subscribed to receive emails when their own commits cause problems. When users are subscribed to receive all emails, its not a problem. There is a link to a mailing list discussion about it as well. It has been resolved, and there is a fix posted on the mailing list. Which can be found here: https://github.com/Kitware/CDash/commit/d8d550e969173067d292db6e91bf9a0d9a4c6276 Clint From jgfouca at sandia.gov Fri May 15 19:40:49 2015 From: jgfouca at sandia.gov (Foucar, James G) Date: Fri, 15 May 2015 19:40:49 +0000 Subject: [Cdash] length of time item remains on dashboard Message-ID: Hello, My current project has a number of "Nightly" tests that run for several days. The issue I'm having is that these builds are posted to CDash and only remain on the Nightly dashboard for about 24 hours. I really love for the dashboard to display a build until a newer build with the same name is submitted. Is this possible? Thanks, -Jim -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Fri May 15 20:21:04 2015 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Fri, 15 May 2015 16:21:04 -0400 Subject: [Cdash] length of time item remains on dashboard In-Reply-To: References: Message-ID: On Fri, May 15, 2015 at 3:40 PM, Foucar, James G wrote: > Hello, > > My current project has a number of ?Nightly? tests that run for several > days. The issue I?m having is that these builds are posted to CDash and > only remain on the Nightly dashboard for about 24 hours. I really love for > the dashboard to display a build until a newer build with the same name is > submitted. Is this possible? > Not that I know of. As you noticed, CDash currently only supports reporting build results on a day to day basis. It would be nice if this behavior could be configured differently per build group: daily, weekly, last N builds, etc. As things are now, the only workaround I can think of would be to resubmit the same .xml files day after day. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgfouca at sandia.gov Fri May 15 21:31:47 2015 From: jgfouca at sandia.gov (Foucar, James G) Date: Fri, 15 May 2015 21:31:47 +0000 Subject: [Cdash] [EXTERNAL] Re: length of time item remains on dashboard In-Reply-To: References: Message-ID: Thanks, I may try that workaround. A related question: According to the Ctest documentation, CTEST_NIGHTLY_START_TIME defines the 24-hour window that a build will be displayed on the dashboard. We have a variety of tests on different machines starting at different times. My goal is to at least get builds on the dashboard for the full 24 hours, so for each build submission, I've defined the nightly start time as the current time. This doesn't appear to be working as I intended because I see some of my tests from last night have already been removed from the dashboard. It's like the CTEST_NIGHTLY_START_TIME being submitted for later builds is impacting all the builds. How does CDash manage the nightly start times? Is it global or per-build? Thanks, -Jim From: Zack Galbreath > Date: Friday, May 15, 2015 at 2:21 PM To: "Foucar, James G" > Cc: "cdash at public.kitware.com" > Subject: [EXTERNAL] Re: [Cdash] length of time item remains on dashboard On Fri, May 15, 2015 at 3:40 PM, Foucar, James G > wrote: Hello, My current project has a number of "Nightly" tests that run for several days. The issue I'm having is that these builds are posted to CDash and only remain on the Nightly dashboard for about 24 hours. I really love for the dashboard to display a build until a newer build with the same name is submitted. Is this possible? Not that I know of. As you noticed, CDash currently only supports reporting build results on a day to day basis. It would be nice if this behavior could be configured differently per build group: daily, weekly, last N builds, etc. As things are now, the only workaround I can think of would be to resubmit the same .xml files day after day. -------------- next part -------------- An HTML attachment was scrubbed... URL: From prwolfe at sandia.gov Sat May 16 01:37:08 2015 From: prwolfe at sandia.gov (Wolfenbarger, Paul R) Date: Sat, 16 May 2015 01:37:08 +0000 Subject: [Cdash] [EXTERNAL] Re: length of time item remains on dashboard In-Reply-To: References: Message-ID: In fact we do have a version of cdash that allows us to do daily or weekly reports. We would like it to be more general than it currently is. ---------------------------------------------------------------------------------------- "The one important thing I have learned over the years is the difference between taking one's work seriously and taking one's self seriously. The first is imperative and the second is disastrous." - Margot Fonteyn, prima ballerina Paul R. Wolfenbarger, P.E., M.S. Computational Simulation Infrastructure DevOps Product Owner Sandia National Laboratories P.O. Box 5800 MS 0845 Albuquerque, NM 87185-0845 505-844-5458 phone prwolfe at sandia.gov ---------------------------------------------------------------------------------------- From: Zack Galbreath > Date: Friday, May 15, 2015 at 2:21 PM To: "Foucar, James G" > Cc: "cdash at public.kitware.com" > Subject: [EXTERNAL] Re: [Cdash] length of time item remains on dashboard On Fri, May 15, 2015 at 3:40 PM, Foucar, James G > wrote: Hello, My current project has a number of "Nightly" tests that run for several days. The issue I'm having is that these builds are posted to CDash and only remain on the Nightly dashboard for about 24 hours. I really love for the dashboard to display a build until a newer build with the same name is submitted. Is this possible? Not that I know of. As you noticed, CDash currently only supports reporting build results on a day to day basis. It would be nice if this behavior could be configured differently per build group: daily, weekly, last N builds, etc. As things are now, the only workaround I can think of would be to resubmit the same .xml files day after day. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristofer.tingdahl at dgbes.com Mon May 18 07:40:08 2015 From: kristofer.tingdahl at dgbes.com (Kristofer Tingdahl) Date: Mon, 18 May 2015 09:40:08 +0200 Subject: [Cdash] Problems e-mailing users about problems in builds In-Reply-To: <1475860.oX9dvKgzdg@stryke> References: <1475860.oX9dvKgzdg@stryke> Message-ID: Dear Clint, thanks, this resolved it! Cheers, Kristofer On Fri, May 15, 2015 at 5:46 PM, Clinton Stimpson wrote: > On Friday, May 15, 2015 04:24:35 PM Kristofer Tingdahl wrote: > > Hi, > > > > I have a CI which is reporting into a dashboard, and I want my users to > get > > an e-mail if they are causing a problem. The problem is that I cannot get > > it working. > > > > I have polluted cdash with add_log to understand what is happening. It > > turns out that the SQL query in NNN, for instance: > > > > SELECT author,email,committeremail FROM updatefile AS uf,build2update AS > > b2u WHERE b2u.updateid=uf.updateid AND b2u.buildid='65962' > > > > > > does never return anything. It turns out that the insert into the > > "build2update" that associates the buildid with the update id comes > later, > > and at that point, no-one is checking if there should be e-mails sent. > > > > > > From the ctest side, I see from the log that it alsways sends the Build > > first, followed by the Configure, and last the Update xml files. Since > the > > insert into build2update comes at when the update is submitted, I tried > to > > reverse the order by having ctest_sumbit (PART ... ), but then I get > > different build-numbers. > > > > Any ideas on how to proceed? > > > > You could first check to see if this covers your problem: > https://public.kitware.com/Bug/view.php?id=15453 > > The debugging you are doing so far sounds much like the debugging I did a > while back. > > Its a problem where users are subscribed to receive emails when their own > commits cause problems. When users are subscribed to receive all emails, > its > not a problem. > > There is a link to a mailing list discussion about it as well. > > It has been resolved, and there is a fix posted on the mailing list. > Which can be found here: > > https://github.com/Kitware/CDash/commit/d8d550e969173067d292db6e91bf9a0d9a4c6276 > > Clint > > -- *Dr. Kristofer Tingdahl**Chief Executive Officer* *______________________________* *dGB Earth Sciences*Phone:+31 53 4315155Skype:dgbtingdahlE-mail: kristofer.tingdahl at dgbes.comInternet:dgbes.com & opendtect.org *______________________________* -------------- next part -------------- An HTML attachment was scrubbed... URL: From vodall at gmail.com Thu May 21 02:43:40 2015 From: vodall at gmail.com (Bill V) Date: Wed, 20 May 2015 19:43:40 -0700 Subject: [Cdash] External programs accessing CTest/CDash database Message-ID: Are there any sample projects available where the CTest database is accessed by scripts outside of the web interface for various data queries and extraction? We'd like to create a CSV file of build timings for reports other than what is currently available. The information to do it is in the CDash scripts but if there's some python or other code available it'll give a good start. I found https://github.com/soonhokong/cdash/blob/master/testSummary.php but that's another web ap. Thanks! Bill From zack.galbreath at kitware.com Thu May 21 13:42:36 2015 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Thu, 21 May 2015 09:42:36 -0400 Subject: [Cdash] External programs accessing CTest/CDash database In-Reply-To: References: Message-ID: On Wed, May 20, 2015 at 10:43 PM, Bill V wrote: > Are there any sample projects available where the CTest database is > accessed by scripts outside of the web interface for various data > queries and extraction? Here's an example Python script used by the VTK developers to more easily track down failing tests: https://github.com/Kitware/VTK/blob/master/Utilities/Maintenance/vtk_fail_summary.py In general, it is a goal of ours to make it easier to access the information in the CDash database. We've made some progress on this recently, but it will still be some time before this effort is complete. > We'd like to create a CSV file of build > timings for reports other than what is currently available. The > information to do it is in the CDash scripts but if there's some > python or other code available it'll give a good start. > Take a look at the documentation here: http://public.kitware.com/Wiki/CDash:API I'm not 100% sure, but the "revisionstatus" task might give you the information that you're seeking. -------------- next part -------------- An HTML attachment was scrubbed... URL: From DLRdave at aol.com Thu May 21 13:58:05 2015 From: DLRdave at aol.com (David Cole) Date: Thu, 21 May 2015 09:58:05 -0400 Subject: [Cdash] External programs accessing CTest/CDash database In-Reply-To: References: Message-ID: There are some python scripts in the VTK code base that pull/poll some data from CDash and report on certain test results. You could probably use that as a guide for figuring out how to do a few things. For example, these three: https://github.com/Kitware/VTK/blob/master/Utilities/Maintenance/vtk_fail_summary.py https://github.com/Kitware/VTK/blob/master/Utilities/Maintenance/vtk_site_history.py https://github.com/Kitware/VTK/blob/master/Utilities/Maintenance/vtk_submitter_summary.py HTH, David C. On Wed, May 20, 2015 at 10:43 PM, Bill V wrote: > Are there any sample projects available where the CTest database is > accessed by scripts outside of the web interface for various data > queries and extraction? We'd like to create a CSV file of build > timings for reports other than what is currently available. The > information to do it is in the CDash scripts but if there's some > python or other code available it'll give a good start. > > I found https://github.com/soonhokong/cdash/blob/master/testSummary.php > but that's another web ap. > > Thanks! > > Bill > _______________________________________________ > Cdash mailing list > Cdash at public.kitware.com > http://public.kitware.com/mailman/listinfo/cdash From kristofer.tingdahl at dgbes.com Thu May 21 14:40:22 2015 From: kristofer.tingdahl at dgbes.com (Kristofer Tingdahl) Date: Thu, 21 May 2015 16:40:22 +0200 Subject: [Cdash] E-mail on new errors, not existing Message-ID: Hi, In the our CDASH - CI implementation, it sometimes happens that a test fails (the world is not perfect - right). If developer A has written that, he will get an e-mail. If developer B commits a bit later a new revision that is completely unrelated to the one A did, it will also fail the test if A has not fixed his crap yet. The problem is that B will also get an e-mail about the failed test which was caused by A. I would wish to filter this a bit, so that B does only get an e-mail if there are NEW problems in the build, i.e. what you see with the +1 signs in the GUI. Is there a way to do that. It is clear that the system can figure out the +1,-1 data, so it should be in there. Any hints anyone? - K -- *Dr. Kristofer Tingdahl**Chief Executive Officer* *______________________________* *dGB Earth Sciences*Phone:+31 53 4315155Skype:dgbtingdahlE-mail: kristofer.tingdahl at dgbes.comInternet:dgbes.com & opendtect.org *______________________________* -------------- next part -------------- An HTML attachment was scrubbed... URL: From vodall at gmail.com Thu May 21 16:42:46 2015 From: vodall at gmail.com (Bill V) Date: Thu, 21 May 2015 09:42:46 -0700 Subject: [Cdash] External programs accessing CTest/CDash database In-Reply-To: References: Message-ID: > Here's an example Python script used by the VTK developers to more easily > track down failing tests: > > https://github.com/Kitware/VTK/blob/master/Utilities/Maintenance/vtk_fail_summary.py > > In general, it is a goal of ours to make it easier to access the information > in the CDash database. We've made some progress on this recently, but it > will still be some time before this effort is complete. Thank you folks - this looks like just what we need. Bill From kristofer.tingdahl at dgbes.com Fri May 15 14:24:35 2015 From: kristofer.tingdahl at dgbes.com (Kristofer Tingdahl) Date: Fri, 15 May 2015 16:24:35 +0200 Subject: [Cdash] Problems e-mailing users about problems in builds Message-ID: Hi, I have a CI which is reporting into a dashboard, and I want my users to get an e-mail if they are causing a problem. The problem is that I cannot get it working. I have polluted cdash with add_log to understand what is happening. It turns out that the SQL query in NNN, for instance: SELECT author,email,committeremail FROM updatefile AS uf,build2update AS b2u WHERE b2u.updateid=uf.updateid AND b2u.buildid='65962' does never return anything. It turns out that the insert into the "build2update" that associates the buildid with the update id comes later, and at that point, no-one is checking if there should be e-mails sent. >From the ctest side, I see from the log that it alsways sends the Build first, followed by the Configure, and last the Update xml files. Since the insert into build2update comes at when the update is submitted, I tried to reverse the order by having ctest_sumbit (PART ... ), but then I get different build-numbers. Any ideas on how to proceed? - Kristofer -- *Dr. Kristofer Tingdahl**Chief Executive Officer* *______________________________* *dGB Earth Sciences*Phone:+31 53 4315155Skype:dgbtingdahlE-mail: kristofer.tingdahl at dgbes.comInternet:dgbes.com & opendtect.org *______________________________* -------------- next part -------------- An HTML attachment was scrubbed... URL: From clinton at elemtech.com Fri May 15 15:46:18 2015 From: clinton at elemtech.com (Clinton Stimpson) Date: Fri, 15 May 2015 09:46:18 -0600 Subject: [Cdash] Problems e-mailing users about problems in builds In-Reply-To: References: Message-ID: <1475860.oX9dvKgzdg@stryke> On Friday, May 15, 2015 04:24:35 PM Kristofer Tingdahl wrote: > Hi, > > I have a CI which is reporting into a dashboard, and I want my users to get > an e-mail if they are causing a problem. The problem is that I cannot get > it working. > > I have polluted cdash with add_log to understand what is happening. It > turns out that the SQL query in NNN, for instance: > > SELECT author,email,committeremail FROM updatefile AS uf,build2update AS > b2u WHERE b2u.updateid=uf.updateid AND b2u.buildid='65962' > > > does never return anything. It turns out that the insert into the > "build2update" that associates the buildid with the update id comes later, > and at that point, no-one is checking if there should be e-mails sent. > > > From the ctest side, I see from the log that it alsways sends the Build > first, followed by the Configure, and last the Update xml files. Since the > insert into build2update comes at when the update is submitted, I tried to > reverse the order by having ctest_sumbit (PART ... ), but then I get > different build-numbers. > > Any ideas on how to proceed? > You could first check to see if this covers your problem: https://public.kitware.com/Bug/view.php?id=15453 The debugging you are doing so far sounds much like the debugging I did a while back. Its a problem where users are subscribed to receive emails when their own commits cause problems. When users are subscribed to receive all emails, its not a problem. There is a link to a mailing list discussion about it as well. It has been resolved, and there is a fix posted on the mailing list. Which can be found here: https://github.com/Kitware/CDash/commit/d8d550e969173067d292db6e91bf9a0d9a4c6276 Clint From jgfouca at sandia.gov Fri May 15 19:40:49 2015 From: jgfouca at sandia.gov (Foucar, James G) Date: Fri, 15 May 2015 19:40:49 +0000 Subject: [Cdash] length of time item remains on dashboard Message-ID: Hello, My current project has a number of "Nightly" tests that run for several days. The issue I'm having is that these builds are posted to CDash and only remain on the Nightly dashboard for about 24 hours. I really love for the dashboard to display a build until a newer build with the same name is submitted. Is this possible? Thanks, -Jim -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Fri May 15 20:21:04 2015 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Fri, 15 May 2015 16:21:04 -0400 Subject: [Cdash] length of time item remains on dashboard In-Reply-To: References: Message-ID: On Fri, May 15, 2015 at 3:40 PM, Foucar, James G wrote: > Hello, > > My current project has a number of ?Nightly? tests that run for several > days. The issue I?m having is that these builds are posted to CDash and > only remain on the Nightly dashboard for about 24 hours. I really love for > the dashboard to display a build until a newer build with the same name is > submitted. Is this possible? > Not that I know of. As you noticed, CDash currently only supports reporting build results on a day to day basis. It would be nice if this behavior could be configured differently per build group: daily, weekly, last N builds, etc. As things are now, the only workaround I can think of would be to resubmit the same .xml files day after day. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgfouca at sandia.gov Fri May 15 21:31:47 2015 From: jgfouca at sandia.gov (Foucar, James G) Date: Fri, 15 May 2015 21:31:47 +0000 Subject: [Cdash] [EXTERNAL] Re: length of time item remains on dashboard In-Reply-To: References: Message-ID: Thanks, I may try that workaround. A related question: According to the Ctest documentation, CTEST_NIGHTLY_START_TIME defines the 24-hour window that a build will be displayed on the dashboard. We have a variety of tests on different machines starting at different times. My goal is to at least get builds on the dashboard for the full 24 hours, so for each build submission, I've defined the nightly start time as the current time. This doesn't appear to be working as I intended because I see some of my tests from last night have already been removed from the dashboard. It's like the CTEST_NIGHTLY_START_TIME being submitted for later builds is impacting all the builds. How does CDash manage the nightly start times? Is it global or per-build? Thanks, -Jim From: Zack Galbreath > Date: Friday, May 15, 2015 at 2:21 PM To: "Foucar, James G" > Cc: "cdash at public.kitware.com" > Subject: [EXTERNAL] Re: [Cdash] length of time item remains on dashboard On Fri, May 15, 2015 at 3:40 PM, Foucar, James G > wrote: Hello, My current project has a number of "Nightly" tests that run for several days. The issue I'm having is that these builds are posted to CDash and only remain on the Nightly dashboard for about 24 hours. I really love for the dashboard to display a build until a newer build with the same name is submitted. Is this possible? Not that I know of. As you noticed, CDash currently only supports reporting build results on a day to day basis. It would be nice if this behavior could be configured differently per build group: daily, weekly, last N builds, etc. As things are now, the only workaround I can think of would be to resubmit the same .xml files day after day. -------------- next part -------------- An HTML attachment was scrubbed... URL: From prwolfe at sandia.gov Sat May 16 01:37:08 2015 From: prwolfe at sandia.gov (Wolfenbarger, Paul R) Date: Sat, 16 May 2015 01:37:08 +0000 Subject: [Cdash] [EXTERNAL] Re: length of time item remains on dashboard In-Reply-To: References: Message-ID: In fact we do have a version of cdash that allows us to do daily or weekly reports. We would like it to be more general than it currently is. ---------------------------------------------------------------------------------------- "The one important thing I have learned over the years is the difference between taking one's work seriously and taking one's self seriously. The first is imperative and the second is disastrous." - Margot Fonteyn, prima ballerina Paul R. Wolfenbarger, P.E., M.S. Computational Simulation Infrastructure DevOps Product Owner Sandia National Laboratories P.O. Box 5800 MS 0845 Albuquerque, NM 87185-0845 505-844-5458 phone prwolfe at sandia.gov ---------------------------------------------------------------------------------------- From: Zack Galbreath > Date: Friday, May 15, 2015 at 2:21 PM To: "Foucar, James G" > Cc: "cdash at public.kitware.com" > Subject: [EXTERNAL] Re: [Cdash] length of time item remains on dashboard On Fri, May 15, 2015 at 3:40 PM, Foucar, James G > wrote: Hello, My current project has a number of "Nightly" tests that run for several days. The issue I'm having is that these builds are posted to CDash and only remain on the Nightly dashboard for about 24 hours. I really love for the dashboard to display a build until a newer build with the same name is submitted. Is this possible? Not that I know of. As you noticed, CDash currently only supports reporting build results on a day to day basis. It would be nice if this behavior could be configured differently per build group: daily, weekly, last N builds, etc. As things are now, the only workaround I can think of would be to resubmit the same .xml files day after day. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristofer.tingdahl at dgbes.com Mon May 18 07:40:08 2015 From: kristofer.tingdahl at dgbes.com (Kristofer Tingdahl) Date: Mon, 18 May 2015 09:40:08 +0200 Subject: [Cdash] Problems e-mailing users about problems in builds In-Reply-To: <1475860.oX9dvKgzdg@stryke> References: <1475860.oX9dvKgzdg@stryke> Message-ID: Dear Clint, thanks, this resolved it! Cheers, Kristofer On Fri, May 15, 2015 at 5:46 PM, Clinton Stimpson wrote: > On Friday, May 15, 2015 04:24:35 PM Kristofer Tingdahl wrote: > > Hi, > > > > I have a CI which is reporting into a dashboard, and I want my users to > get > > an e-mail if they are causing a problem. The problem is that I cannot get > > it working. > > > > I have polluted cdash with add_log to understand what is happening. It > > turns out that the SQL query in NNN, for instance: > > > > SELECT author,email,committeremail FROM updatefile AS uf,build2update AS > > b2u WHERE b2u.updateid=uf.updateid AND b2u.buildid='65962' > > > > > > does never return anything. It turns out that the insert into the > > "build2update" that associates the buildid with the update id comes > later, > > and at that point, no-one is checking if there should be e-mails sent. > > > > > > From the ctest side, I see from the log that it alsways sends the Build > > first, followed by the Configure, and last the Update xml files. Since > the > > insert into build2update comes at when the update is submitted, I tried > to > > reverse the order by having ctest_sumbit (PART ... ), but then I get > > different build-numbers. > > > > Any ideas on how to proceed? > > > > You could first check to see if this covers your problem: > https://public.kitware.com/Bug/view.php?id=15453 > > The debugging you are doing so far sounds much like the debugging I did a > while back. > > Its a problem where users are subscribed to receive emails when their own > commits cause problems. When users are subscribed to receive all emails, > its > not a problem. > > There is a link to a mailing list discussion about it as well. > > It has been resolved, and there is a fix posted on the mailing list. > Which can be found here: > > https://github.com/Kitware/CDash/commit/d8d550e969173067d292db6e91bf9a0d9a4c6276 > > Clint > > -- *Dr. Kristofer Tingdahl**Chief Executive Officer* *______________________________* *dGB Earth Sciences*Phone:+31 53 4315155Skype:dgbtingdahlE-mail: kristofer.tingdahl at dgbes.comInternet:dgbes.com & opendtect.org *______________________________* -------------- next part -------------- An HTML attachment was scrubbed... URL: From vodall at gmail.com Thu May 21 02:43:40 2015 From: vodall at gmail.com (Bill V) Date: Wed, 20 May 2015 19:43:40 -0700 Subject: [Cdash] External programs accessing CTest/CDash database Message-ID: Are there any sample projects available where the CTest database is accessed by scripts outside of the web interface for various data queries and extraction? We'd like to create a CSV file of build timings for reports other than what is currently available. The information to do it is in the CDash scripts but if there's some python or other code available it'll give a good start. I found https://github.com/soonhokong/cdash/blob/master/testSummary.php but that's another web ap. Thanks! Bill From zack.galbreath at kitware.com Thu May 21 13:42:36 2015 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Thu, 21 May 2015 09:42:36 -0400 Subject: [Cdash] External programs accessing CTest/CDash database In-Reply-To: References: Message-ID: On Wed, May 20, 2015 at 10:43 PM, Bill V wrote: > Are there any sample projects available where the CTest database is > accessed by scripts outside of the web interface for various data > queries and extraction? Here's an example Python script used by the VTK developers to more easily track down failing tests: https://github.com/Kitware/VTK/blob/master/Utilities/Maintenance/vtk_fail_summary.py In general, it is a goal of ours to make it easier to access the information in the CDash database. We've made some progress on this recently, but it will still be some time before this effort is complete. > We'd like to create a CSV file of build > timings for reports other than what is currently available. The > information to do it is in the CDash scripts but if there's some > python or other code available it'll give a good start. > Take a look at the documentation here: http://public.kitware.com/Wiki/CDash:API I'm not 100% sure, but the "revisionstatus" task might give you the information that you're seeking. -------------- next part -------------- An HTML attachment was scrubbed... URL: From DLRdave at aol.com Thu May 21 13:58:05 2015 From: DLRdave at aol.com (David Cole) Date: Thu, 21 May 2015 09:58:05 -0400 Subject: [Cdash] External programs accessing CTest/CDash database In-Reply-To: References: Message-ID: There are some python scripts in the VTK code base that pull/poll some data from CDash and report on certain test results. You could probably use that as a guide for figuring out how to do a few things. For example, these three: https://github.com/Kitware/VTK/blob/master/Utilities/Maintenance/vtk_fail_summary.py https://github.com/Kitware/VTK/blob/master/Utilities/Maintenance/vtk_site_history.py https://github.com/Kitware/VTK/blob/master/Utilities/Maintenance/vtk_submitter_summary.py HTH, David C. On Wed, May 20, 2015 at 10:43 PM, Bill V wrote: > Are there any sample projects available where the CTest database is > accessed by scripts outside of the web interface for various data > queries and extraction? We'd like to create a CSV file of build > timings for reports other than what is currently available. The > information to do it is in the CDash scripts but if there's some > python or other code available it'll give a good start. > > I found https://github.com/soonhokong/cdash/blob/master/testSummary.php > but that's another web ap. > > Thanks! > > Bill > _______________________________________________ > Cdash mailing list > Cdash at public.kitware.com > http://public.kitware.com/mailman/listinfo/cdash From kristofer.tingdahl at dgbes.com Thu May 21 14:40:22 2015 From: kristofer.tingdahl at dgbes.com (Kristofer Tingdahl) Date: Thu, 21 May 2015 16:40:22 +0200 Subject: [Cdash] E-mail on new errors, not existing Message-ID: Hi, In the our CDASH - CI implementation, it sometimes happens that a test fails (the world is not perfect - right). If developer A has written that, he will get an e-mail. If developer B commits a bit later a new revision that is completely unrelated to the one A did, it will also fail the test if A has not fixed his crap yet. The problem is that B will also get an e-mail about the failed test which was caused by A. I would wish to filter this a bit, so that B does only get an e-mail if there are NEW problems in the build, i.e. what you see with the +1 signs in the GUI. Is there a way to do that. It is clear that the system can figure out the +1,-1 data, so it should be in there. Any hints anyone? - K -- *Dr. Kristofer Tingdahl**Chief Executive Officer* *______________________________* *dGB Earth Sciences*Phone:+31 53 4315155Skype:dgbtingdahlE-mail: kristofer.tingdahl at dgbes.comInternet:dgbes.com & opendtect.org *______________________________* -------------- next part -------------- An HTML attachment was scrubbed... URL: From vodall at gmail.com Thu May 21 16:42:46 2015 From: vodall at gmail.com (Bill V) Date: Thu, 21 May 2015 09:42:46 -0700 Subject: [Cdash] External programs accessing CTest/CDash database In-Reply-To: References: Message-ID: > Here's an example Python script used by the VTK developers to more easily > track down failing tests: > > https://github.com/Kitware/VTK/blob/master/Utilities/Maintenance/vtk_fail_summary.py > > In general, it is a goal of ours to make it easier to access the information > in the CDash database. We've made some progress on this recently, but it > will still be some time before this effort is complete. Thank you folks - this looks like just what we need. Bill