From glhenni at sandia.gov Fri Oct 19 12:12:42 2018 From: glhenni at sandia.gov (Gary Hennigan) Date: Fri, 19 Oct 2018 10:12:42 -0600 Subject: [CDash] Problems with 2.4.0 upgrade Message-ID: <1dc4f30c-6ee8-f6f0-dcf1-51b1028387f5@sandia.gov> We've been using cdash 2.2.2 for quite a while but the server running it is going to be decommissioned so I thought I'd take the opportunity to upgrade to 2.4.0 (although it says 2.5.0 on the bottom of the dashboard). So I clone the repository and switch to the /v2.4.0-prebuilt/ tag and point the webserver right to the clone. I've got two problems I've been fighting since the install... Problem one, last night all our regression tests completed successfully and all submitted to cdash but one of the expected builds is absent from the database. The submission reported as successfully completed by the test execution platform, I can see, in the job's log, the successful submission of the XML files to my cdash site, I can see the submitted files associated with the job in the /CDash/backup/ directory, but I see nothing for that job in the database and therefore, of course, the dashboard is showing an empty line for that particular test with /Expected build/ in the *Start Time* column. It appears the job is being successfully submitted but not inserted into the database. Problem two, false negatives in email. The first time this happened I had inadvertently enabled test timing and since it was starting from scratch the times were varying. Just looking at the dashboard there was no indication of this until I turned on the /Advanced View. /Then I could see a red column for timings and I figured out what was going on and disabled test timing. However, that didn't completely eliminate the problem. Again, last night all our regression tests passed and aside from the aforementioned missing build in the database, all the columns are green. But I got the following email: A submission to CDash for the project Charon has failing tests. You have been identified as one of the authors who have checked in changes that are part of this submission or you are listed in the default contact list. Details on the submission can be found athttp://cdashmachine.my.url/cdash/buildSummary.php?buildid=252 Project: Charon Site: CEE Build Farm Build Name: Linux-x86_64-RHEL_6.x-SEMS_OpenMPI_1.10_Intel_17.x-DBG Build Time: 2018-10-19T01:00:16 UTC Type: Nightly Tests failing: 3 -CDash on cdashmachine.my.url I follow the link and I see: Current Build Stage Errors Warnings *Update* *0 * *0 * *Configure* *0 * *0 * *Build* *0 * *0 * *Test* *0 * *0 * So those 3 failing tests are showing up here. Now if I look at the bottom of the page, and I select "View Tests Summary" I get a clue *107 passed, 0 failed, 3 timed out, 0 not run. *I don't know where that /"3 timed out"/ is coming from and they don't show up in the table associated with this test summary below that. This test suite does have 110 tests, but 3 of them are excluded from this particular platform/compiler combination via a "-LE debugexclude" and tagging those three tests with a "debugexclude". I can't for the life of me figure out why it thinks three tests have "timed out". One thing that could be an issue, maybe related to both my problems, is uniqueness. Does "BuildName" have to be unique? Typically, in our case, only the combination of "BuildName" and "Name" are unique. Also we use jenkins for some of our testing and the platform/site that those tests run on isn't stable. Each night the tests may run on a different machine in the jenkins build farm. In those tests we set the value of "Name" by using SET(CTEST_SITE ). Maybe I'm just grasping at straws here. Lastly, almost nothing has changed in how we're doing things. I simply changed our submissions from the old 2.2.2 CDash, which was working fine, to my new install of 2.4.0 on a new platform. Hopefully someone can offer some suggestions on my likely overly detailed description, or at least how to start to debug it. Thanks, Gary ** -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Fri Oct 19 12:27:42 2018 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Fri, 19 Oct 2018 12:27:42 -0400 Subject: [CDash] Problems with 2.4.0 upgrade In-Reply-To: <1dc4f30c-6ee8-f6f0-dcf1-51b1028387f5@sandia.gov> References: <1dc4f30c-6ee8-f6f0-dcf1-51b1028387f5@sandia.gov> Message-ID: On Fri, Oct 19, 2018 at 12:12 PM Gary Hennigan via CDash < cdash at public.kitware.com> wrote: > We've been using cdash 2.2.2 for quite a while but the server running it > is going to be decommissioned so I thought I'd take the opportunity to > upgrade to 2.4.0 (although it says 2.5.0 on the bottom of the dashboard). > So I clone the repository and switch to the *v2.4.0-prebuilt* tag and > point the webserver right to the clone. I've got two problems I've been > fighting since the install... > Did you click the "Upgrade CDash" button after you switched to v2.4.0-prebuilt? This is when any changes to the database structure take place. Log in as an administrator, and then under the "Administration" section of user.php click on "Maintenance". On the following page click the "Upgrade CDash" button. -------------- next part -------------- An HTML attachment was scrubbed... URL: From glhenni at sandia.gov Fri Oct 19 12:34:08 2018 From: glhenni at sandia.gov (Gary Hennigan) Date: Fri, 19 Oct 2018 10:34:08 -0600 Subject: [CDash] [EXTERNAL] Re: Problems with 2.4.0 upgrade In-Reply-To: References: <1dc4f30c-6ee8-f6f0-dcf1-51b1028387f5@sandia.gov> Message-ID: I created the database from scratch on the new CDash server using the procedure outlined in the wiki. I didn't bother trying to copy over our previous 2.2.2 database, and so the new server had no database prior to the installation of 2.4.0. On 10/19/18 10:27, Zack Galbreath wrote: > On Fri, Oct 19, 2018 at 12:12 PM Gary Hennigan via CDash > > wrote: > > We've been using cdash 2.2.2 for quite a while but the server > running it is going to be decommissioned so I thought I'd take the > opportunity to upgrade to 2.4.0 (although it says 2.5.0 on the > bottom of the dashboard). So I clone the repository and switch to > the /v2.4.0-prebuilt/ tag and point the webserver right to the > clone. I've got two problems I've been fighting since the install... > > > Did you click the "Upgrade CDash" button after you switched to > v2.4.0-prebuilt?? This is when any changes to the database structure > take place. > > Log in as an administrator, and then under the "Administration" > section of user.php click on "Maintenance".? On the following page > click the "Upgrade CDash" button. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jcfr at kitware.com Mon Oct 22 11:58:18 2018 From: jcfr at kitware.com (Jean-Christophe Fillion-Robin) Date: Mon, 22 Oct 2018 11:58:18 -0400 Subject: [CDash] Wiki template for marking obsolete section Message-ID: Hi Folks, Following the example of the ITK wiki, I created a wiki template called HistoricalCDash [1] It can be used to label selection of the documentation as historical and out-of-date. For example it is now used to label the older API. See https://cmake.org/Wiki/CDash:API [1] The prefix CDash was added because VTK, ITK, ... and CDash are hosted on the same instance and the template needed to be differentiated. Thanks Jc -------------- next part -------------- An HTML attachment was scrubbed... URL: From glhenni at sandia.gov Fri Oct 19 16:12:42 2018 From: glhenni at sandia.gov (Gary Hennigan) Date: Fri, 19 Oct 2018 10:12:42 -0600 Subject: [CDash] Problems with 2.4.0 upgrade Message-ID: <1dc4f30c-6ee8-f6f0-dcf1-51b1028387f5@sandia.gov> We've been using cdash 2.2.2 for quite a while but the server running it is going to be decommissioned so I thought I'd take the opportunity to upgrade to 2.4.0 (although it says 2.5.0 on the bottom of the dashboard). So I clone the repository and switch to the /v2.4.0-prebuilt/ tag and point the webserver right to the clone. I've got two problems I've been fighting since the install... Problem one, last night all our regression tests completed successfully and all submitted to cdash but one of the expected builds is absent from the database. The submission reported as successfully completed by the test execution platform, I can see, in the job's log, the successful submission of the XML files to my cdash site, I can see the submitted files associated with the job in the /CDash/backup/ directory, but I see nothing for that job in the database and therefore, of course, the dashboard is showing an empty line for that particular test with /Expected build/ in the *Start Time* column. It appears the job is being successfully submitted but not inserted into the database. Problem two, false negatives in email. The first time this happened I had inadvertently enabled test timing and since it was starting from scratch the times were varying. Just looking at the dashboard there was no indication of this until I turned on the /Advanced View. /Then I could see a red column for timings and I figured out what was going on and disabled test timing. However, that didn't completely eliminate the problem. Again, last night all our regression tests passed and aside from the aforementioned missing build in the database, all the columns are green. But I got the following email: A submission to CDash for the project Charon has failing tests. You have been identified as one of the authors who have checked in changes that are part of this submission or you are listed in the default contact list. Details on the submission can be found athttp://cdashmachine.my.url/cdash/buildSummary.php?buildid=252 Project: Charon Site: CEE Build Farm Build Name: Linux-x86_64-RHEL_6.x-SEMS_OpenMPI_1.10_Intel_17.x-DBG Build Time: 2018-10-19T01:00:16 UTC Type: Nightly Tests failing: 3 -CDash on cdashmachine.my.url I follow the link and I see: Current Build Stage Errors Warnings *Update* *0 * *0 * *Configure* *0 * *0 * *Build* *0 * *0 * *Test* *0 * *0 * So those 3 failing tests are showing up here. Now if I look at the bottom of the page, and I select "View Tests Summary" I get a clue *107 passed, 0 failed, 3 timed out, 0 not run. *I don't know where that /"3 timed out"/ is coming from and they don't show up in the table associated with this test summary below that. This test suite does have 110 tests, but 3 of them are excluded from this particular platform/compiler combination via a "-LE debugexclude" and tagging those three tests with a "debugexclude". I can't for the life of me figure out why it thinks three tests have "timed out". One thing that could be an issue, maybe related to both my problems, is uniqueness. Does "BuildName" have to be unique? Typically, in our case, only the combination of "BuildName" and "Name" are unique. Also we use jenkins for some of our testing and the platform/site that those tests run on isn't stable. Each night the tests may run on a different machine in the jenkins build farm. In those tests we set the value of "Name" by using SET(CTEST_SITE ). Maybe I'm just grasping at straws here. Lastly, almost nothing has changed in how we're doing things. I simply changed our submissions from the old 2.2.2 CDash, which was working fine, to my new install of 2.4.0 on a new platform. Hopefully someone can offer some suggestions on my likely overly detailed description, or at least how to start to debug it. Thanks, Gary ** -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Fri Oct 19 16:27:42 2018 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Fri, 19 Oct 2018 12:27:42 -0400 Subject: [CDash] Problems with 2.4.0 upgrade In-Reply-To: <1dc4f30c-6ee8-f6f0-dcf1-51b1028387f5@sandia.gov> References: <1dc4f30c-6ee8-f6f0-dcf1-51b1028387f5@sandia.gov> Message-ID: On Fri, Oct 19, 2018 at 12:12 PM Gary Hennigan via CDash < cdash at public.kitware.com> wrote: > We've been using cdash 2.2.2 for quite a while but the server running it > is going to be decommissioned so I thought I'd take the opportunity to > upgrade to 2.4.0 (although it says 2.5.0 on the bottom of the dashboard). > So I clone the repository and switch to the *v2.4.0-prebuilt* tag and > point the webserver right to the clone. I've got two problems I've been > fighting since the install... > Did you click the "Upgrade CDash" button after you switched to v2.4.0-prebuilt? This is when any changes to the database structure take place. Log in as an administrator, and then under the "Administration" section of user.php click on "Maintenance". On the following page click the "Upgrade CDash" button. -------------- next part -------------- An HTML attachment was scrubbed... URL: From glhenni at sandia.gov Fri Oct 19 16:34:08 2018 From: glhenni at sandia.gov (Gary Hennigan) Date: Fri, 19 Oct 2018 10:34:08 -0600 Subject: [CDash] [EXTERNAL] Re: Problems with 2.4.0 upgrade In-Reply-To: References: <1dc4f30c-6ee8-f6f0-dcf1-51b1028387f5@sandia.gov> Message-ID: I created the database from scratch on the new CDash server using the procedure outlined in the wiki. I didn't bother trying to copy over our previous 2.2.2 database, and so the new server had no database prior to the installation of 2.4.0. On 10/19/18 10:27, Zack Galbreath wrote: > On Fri, Oct 19, 2018 at 12:12 PM Gary Hennigan via CDash > > wrote: > > We've been using cdash 2.2.2 for quite a while but the server > running it is going to be decommissioned so I thought I'd take the > opportunity to upgrade to 2.4.0 (although it says 2.5.0 on the > bottom of the dashboard). So I clone the repository and switch to > the /v2.4.0-prebuilt/ tag and point the webserver right to the > clone. I've got two problems I've been fighting since the install... > > > Did you click the "Upgrade CDash" button after you switched to > v2.4.0-prebuilt?? This is when any changes to the database structure > take place. > > Log in as an administrator, and then under the "Administration" > section of user.php click on "Maintenance".? On the following page > click the "Upgrade CDash" button. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jcfr at kitware.com Mon Oct 22 15:58:18 2018 From: jcfr at kitware.com (Jean-Christophe Fillion-Robin) Date: Mon, 22 Oct 2018 11:58:18 -0400 Subject: [CDash] Wiki template for marking obsolete section Message-ID: Hi Folks, Following the example of the ITK wiki, I created a wiki template called HistoricalCDash [1] It can be used to label selection of the documentation as historical and out-of-date. For example it is now used to label the older API. See https://cmake.org/Wiki/CDash:API [1] The prefix CDash was added because VTK, ITK, ... and CDash are hosted on the same instance and the template needed to be differentiated. Thanks Jc -------------- next part -------------- An HTML attachment was scrubbed... URL: From glhenni at sandia.gov Fri Oct 19 16:12:42 2018 From: glhenni at sandia.gov (Gary Hennigan) Date: Fri, 19 Oct 2018 10:12:42 -0600 Subject: [CDash] Problems with 2.4.0 upgrade Message-ID: <1dc4f30c-6ee8-f6f0-dcf1-51b1028387f5@sandia.gov> We've been using cdash 2.2.2 for quite a while but the server running it is going to be decommissioned so I thought I'd take the opportunity to upgrade to 2.4.0 (although it says 2.5.0 on the bottom of the dashboard). So I clone the repository and switch to the /v2.4.0-prebuilt/ tag and point the webserver right to the clone. I've got two problems I've been fighting since the install... Problem one, last night all our regression tests completed successfully and all submitted to cdash but one of the expected builds is absent from the database. The submission reported as successfully completed by the test execution platform, I can see, in the job's log, the successful submission of the XML files to my cdash site, I can see the submitted files associated with the job in the /CDash/backup/ directory, but I see nothing for that job in the database and therefore, of course, the dashboard is showing an empty line for that particular test with /Expected build/ in the *Start Time* column. It appears the job is being successfully submitted but not inserted into the database. Problem two, false negatives in email. The first time this happened I had inadvertently enabled test timing and since it was starting from scratch the times were varying. Just looking at the dashboard there was no indication of this until I turned on the /Advanced View. /Then I could see a red column for timings and I figured out what was going on and disabled test timing. However, that didn't completely eliminate the problem. Again, last night all our regression tests passed and aside from the aforementioned missing build in the database, all the columns are green. But I got the following email: A submission to CDash for the project Charon has failing tests. You have been identified as one of the authors who have checked in changes that are part of this submission or you are listed in the default contact list. Details on the submission can be found athttp://cdashmachine.my.url/cdash/buildSummary.php?buildid=252 Project: Charon Site: CEE Build Farm Build Name: Linux-x86_64-RHEL_6.x-SEMS_OpenMPI_1.10_Intel_17.x-DBG Build Time: 2018-10-19T01:00:16 UTC Type: Nightly Tests failing: 3 -CDash on cdashmachine.my.url I follow the link and I see: Current Build Stage Errors Warnings *Update* *0 * *0 * *Configure* *0 * *0 * *Build* *0 * *0 * *Test* *0 * *0 * So those 3 failing tests are showing up here. Now if I look at the bottom of the page, and I select "View Tests Summary" I get a clue *107 passed, 0 failed, 3 timed out, 0 not run. *I don't know where that /"3 timed out"/ is coming from and they don't show up in the table associated with this test summary below that. This test suite does have 110 tests, but 3 of them are excluded from this particular platform/compiler combination via a "-LE debugexclude" and tagging those three tests with a "debugexclude". I can't for the life of me figure out why it thinks three tests have "timed out". One thing that could be an issue, maybe related to both my problems, is uniqueness. Does "BuildName" have to be unique? Typically, in our case, only the combination of "BuildName" and "Name" are unique. Also we use jenkins for some of our testing and the platform/site that those tests run on isn't stable. Each night the tests may run on a different machine in the jenkins build farm. In those tests we set the value of "Name" by using SET(CTEST_SITE ). Maybe I'm just grasping at straws here. Lastly, almost nothing has changed in how we're doing things. I simply changed our submissions from the old 2.2.2 CDash, which was working fine, to my new install of 2.4.0 on a new platform. Hopefully someone can offer some suggestions on my likely overly detailed description, or at least how to start to debug it. Thanks, Gary ** -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Fri Oct 19 16:27:42 2018 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Fri, 19 Oct 2018 12:27:42 -0400 Subject: [CDash] Problems with 2.4.0 upgrade In-Reply-To: <1dc4f30c-6ee8-f6f0-dcf1-51b1028387f5@sandia.gov> References: <1dc4f30c-6ee8-f6f0-dcf1-51b1028387f5@sandia.gov> Message-ID: On Fri, Oct 19, 2018 at 12:12 PM Gary Hennigan via CDash < cdash at public.kitware.com> wrote: > We've been using cdash 2.2.2 for quite a while but the server running it > is going to be decommissioned so I thought I'd take the opportunity to > upgrade to 2.4.0 (although it says 2.5.0 on the bottom of the dashboard). > So I clone the repository and switch to the *v2.4.0-prebuilt* tag and > point the webserver right to the clone. I've got two problems I've been > fighting since the install... > Did you click the "Upgrade CDash" button after you switched to v2.4.0-prebuilt? This is when any changes to the database structure take place. Log in as an administrator, and then under the "Administration" section of user.php click on "Maintenance". On the following page click the "Upgrade CDash" button. -------------- next part -------------- An HTML attachment was scrubbed... URL: From glhenni at sandia.gov Fri Oct 19 16:34:08 2018 From: glhenni at sandia.gov (Gary Hennigan) Date: Fri, 19 Oct 2018 10:34:08 -0600 Subject: [CDash] [EXTERNAL] Re: Problems with 2.4.0 upgrade In-Reply-To: References: <1dc4f30c-6ee8-f6f0-dcf1-51b1028387f5@sandia.gov> Message-ID: I created the database from scratch on the new CDash server using the procedure outlined in the wiki. I didn't bother trying to copy over our previous 2.2.2 database, and so the new server had no database prior to the installation of 2.4.0. On 10/19/18 10:27, Zack Galbreath wrote: > On Fri, Oct 19, 2018 at 12:12 PM Gary Hennigan via CDash > > wrote: > > We've been using cdash 2.2.2 for quite a while but the server > running it is going to be decommissioned so I thought I'd take the > opportunity to upgrade to 2.4.0 (although it says 2.5.0 on the > bottom of the dashboard). So I clone the repository and switch to > the /v2.4.0-prebuilt/ tag and point the webserver right to the > clone. I've got two problems I've been fighting since the install... > > > Did you click the "Upgrade CDash" button after you switched to > v2.4.0-prebuilt?? This is when any changes to the database structure > take place. > > Log in as an administrator, and then under the "Administration" > section of user.php click on "Maintenance".? On the following page > click the "Upgrade CDash" button. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jcfr at kitware.com Mon Oct 22 15:58:18 2018 From: jcfr at kitware.com (Jean-Christophe Fillion-Robin) Date: Mon, 22 Oct 2018 11:58:18 -0400 Subject: [CDash] Wiki template for marking obsolete section Message-ID: Hi Folks, Following the example of the ITK wiki, I created a wiki template called HistoricalCDash [1] It can be used to label selection of the documentation as historical and out-of-date. For example it is now used to label the older API. See https://cmake.org/Wiki/CDash:API [1] The prefix CDash was added because VTK, ITK, ... and CDash are hosted on the same instance and the template needed to be differentiated. Thanks Jc -------------- next part -------------- An HTML attachment was scrubbed... URL: