From christian.morales.vega at gmail.com Mon Mar 4 04:03:15 2019 From: christian.morales.vega at gmail.com (Cristian Morales Vega) Date: Mon, 4 Mar 2019 09:03:15 +0000 Subject: [CDash] The "Bug Tracker" link in www.cdash.org/ is dead Message-ID: https://www.cdash.org/ "Bug Tracker" section points to either https://public.kitware.com/Bug/view_all_bug_page.php https://public.kitware.com/Bug/set_project.php?ref=view_all_set.php&project_id=23 Depending on whether you go first through https://www.cdash.org/developer-tools/. Both links are dead. FWIW I notice this because I wanted to open an issue for the CDash part of https://gitlab.kitware.com/cmake/cmake/issues/19003 i.e. there doesn't seem to be a way to have a "Dynamic Analysis" of a single "build" with two different "Checkers" (e.g. AddressSanitizer and UndefinedBehaviorSanitizer). From zack.galbreath at kitware.com Mon Mar 4 09:47:20 2019 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Mon, 4 Mar 2019 09:47:20 -0500 Subject: [CDash] The "Bug Tracker" link in www.cdash.org/ is dead In-Reply-To: References: Message-ID: On Mon, Mar 4, 2019 at 4:03 AM Cristian Morales Vega < christian.morales.vega at gmail.com> wrote: > https://www.cdash.org/ "Bug Tracker" section points to either > > https://public.kitware.com/Bug/view_all_bug_page.php > > https://public.kitware.com/Bug/set_project.php?ref=view_all_set.php&project_id=23 > > Depending on whether you go first through > https://www.cdash.org/developer-tools/. Both links are dead. > Thanks for letting us know. This should now point to the correct location. https://github.com/Kitware/CDash/issues -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Mon Mar 4 13:05:37 2019 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Mon, 4 Mar 2019 13:05:37 -0500 Subject: [CDash] Submitted "files" presentation In-Reply-To: References: Message-ID: On Tue, Feb 26, 2019 at 11:57 AM Cristian Morales Vega < christian.morales.vega at gmail.com> wrote: > On Tue, 26 Feb 2019 at 16:07, Cristian Morales Vega > wrote: > > ctest_submit() let's you submit PARTS, but also FILES. I have > > submitted a file with the output of "llvm-cov" with Source-based Code > > Coverage. I know CDash only supports gcov coverage right now, I don't > > expect to get full support for it. But I was hoping to be able to > > access the submitted file somehow from the CDash web view, linked > > somehow to the build. Maybe some "Extra files" section or something. > > I have actually managed to get what I wanted with ctest_upload(). Not > really sure what's supposed to be the difference, though. > I'm glad you figured out how to upload your file to CDash. In my experience, `ctest_submit(FILES ...)` is mostly used for manually submitting CTest XML files that have been generated previously. As you discovered, `ctest_upload` allows you to associate arbitrary files or URLs with your build. -------------- next part -------------- An HTML attachment was scrubbed... URL: From christian.morales.vega at gmail.com Mon Mar 4 15:06:25 2019 From: christian.morales.vega at gmail.com (Cristian Morales Vega) Date: Mon, 4 Mar 2019 20:06:25 +0000 Subject: [CDash] Submitted "files" presentation In-Reply-To: References: Message-ID: On Mon, 4 Mar 2019 at 18:05, Zack Galbreath wrote: > > On Tue, Feb 26, 2019 at 11:57 AM Cristian Morales Vega wrote: >> >> On Tue, 26 Feb 2019 at 16:07, Cristian Morales Vega >> wrote: >> > ctest_submit() let's you submit PARTS, but also FILES. I have >> > submitted a file with the output of "llvm-cov" with Source-based Code >> > Coverage. I know CDash only supports gcov coverage right now, I don't >> > expect to get full support for it. But I was hoping to be able to >> > access the submitted file somehow from the CDash web view, linked >> > somehow to the build. Maybe some "Extra files" section or something. >> >> I have actually managed to get what I wanted with ctest_upload(). Not >> really sure what's supposed to be the difference, though. > > > > I'm glad you figured out how to upload your file to CDash. > > In my experience, `ctest_submit(FILES ...)` is mostly used for manually submitting CTest XML files that have been generated previously. > > As you discovered, `ctest_upload` allows you to associate arbitrary files or URLs with your build. I have yet to try, but I'm now wondering what's the difference between the "Notes", "ExtraFiles" and "Upload" "PARTS". Notice that CTEST_NOTES_FILES and CTEST_EXTRA_SUBMIT_FILES don't appear in https://cmake.org/cmake/help/latest/manual/cmake-variables.7.html#variables-for-ctest. About "ctest_submit(FILES ...)". I have seen that https://blog.kitware.com/wp-content/uploads/2016/02/subproject_coverage_example.tar.gz from https://blog.kitware.com/additional-coverage-features-in-cdash/ does use it to send a Project.xml to create subprojects. But I have not seen that documented elsewhere and now I'm asking myself what other magic xml types can I send to do magic stuff... not curious enough yet to learn PHP, though :-) From martinma at ornl.gov Wed Mar 6 13:49:17 2019 From: martinma at ornl.gov (Martin, Mark) Date: Wed, 6 Mar 2019 18:49:17 +0000 Subject: [CDash] LDAP Authentication Issues Message-ID: <8fad53c13575444f812632c2edac3ddf@EXCHCS31.ornl.gov> Hello, I've established a CDash and have successfully authenticated, via database authentication, the original admin user. However, I am experiencing difficulty authenticating other users via LDAP. My LDAP configuration, generally speaking, looks like this: $CDASH_USE_LDAP = '1'; $CDASH_LDAP_HOSTNAME = 'myldapserver.mydomain.com'; $CDASH_LDAP_BASEDN = 'ou=Users,dc=mydc,dc=mydc2'; $CDASH_LDAP_PROTOCOL_VERSION = '3'; I have concern that CDash may not be able to connect via ldaps://myldapserver.mydomain.com/. I am experiencing a login screen that just spins (loading) for ~3 minutes before refreshing the login screen. No error messages are being generated in the cdash.log file and no error messages are being displayed in the UI. Does anyone have any thoughts or advice on how I should proceed? Best regards, -Mark -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Wed Mar 6 14:08:31 2019 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Wed, 6 Mar 2019 14:08:31 -0500 Subject: [CDash] Branch Coverage with GCov In-Reply-To: References: Message-ID: On Mon, Feb 25, 2019 at 12:54 PM Cristian Morales Vega < christian.morales.vega at gmail.com> wrote: > I'm wondering why the script uses ctest_coverage_collect_gcov() instead of > ctest_coverage() > When we implemented branch coverage in CDash, we made the design decision to let CDash handle the parsing. Previously coverage data was parsed by CTest (generating Coverage.xml and CoverageLog.xml) and then uploaded to CDash. With this new approach we now upload the .gcov files directly to CDash and parse them server-side instead. As to why this isn't working for you, I'm not sure. Do you see the uploaded gcov.tar file in your backup/ directory on the CDash server? -------------- next part -------------- An HTML attachment was scrubbed... URL: From christian.morales.vega at gmail.com Wed Mar 6 14:24:53 2019 From: christian.morales.vega at gmail.com (Cristian Morales Vega) Date: Wed, 6 Mar 2019 19:24:53 +0000 Subject: [CDash] Branch Coverage with GCov In-Reply-To: References: Message-ID: On Wed, 6 Mar 2019 at 19:08, Zack Galbreath wrote: > > On Mon, Feb 25, 2019 at 12:54 PM Cristian Morales Vega wrote: >> >> I'm wondering why the script uses ctest_coverage_collect_gcov() instead of ctest_coverage() > > > When we implemented branch coverage in CDash, we made the design decision to let CDash handle the parsing. Previously coverage data was parsed by CTest (generating Coverage.xml and CoverageLog.xml) and then uploaded to CDash. With this new approach we now upload the .gcov files directly to CDash and parse them server-side instead. > > As to why this isn't working for you, I'm not sure. Do you see the uploaded gcov.tar file in your backup/ directory on the CDash server? Knowing it's only supposed to work with ctest_coverage_collect_gcov() I will look further tomorrow. Thanks. But does this mean ctest_coverage() is deprecated and ctest_coverage_collect_gcov() is a strict superset? While reading the docs I got the impression ctest_coverage() is *the* way, with ctest_coverage_collect_gcov() something you notice while reading about something else, not too clear why it does exist. From sebastien.dinot at c-s.fr Fri Mar 8 05:07:48 2019 From: sebastien.dinot at c-s.fr (=?UTF-8?Q?S=c3=a9bastien_Dinot?=) Date: Fri, 8 Mar 2019 11:07:48 +0100 Subject: [CDash] Database schema doesn't match the version of CDash Message-ID: <28db1225-2540-5c85-0ab1-9ef952b910a8@c-s.fr> Dear all, As explained in my comment of issue #780 on Github , I have a problem when updating the database schema. I tried to migrate the dashboard of Orfeo Toolbox from CDash 2.2.3 to CDash 2.6.0. After installing the sources of version 2.6.0 and following the instructions given on the "Upgrading CDash " page, I visited the CDash maintenance page. I clicked a first time on the "Upgrade CDash" button and the patches for the version 2.4 were applied. I then clicked a second time and the following messages were displayed: Upgrading tables: Applying 2.8 patches: CDash Upgrade Successful. As far as I know, the version 2.8 doesn't exist yet. So, this message is surprising and, indeed, the following message still appears on the home page: The current database schema doesn't match the version of CDash you are running, upgrade your database structure in the Administration/CDash maintenance panel of CDash. What is the best way to correct this problem? Thank you in advance, S?bastien -------------- next part -------------- An HTML attachment was scrubbed... URL: From Pavlech.Juraj at azd.cz Tue Mar 19 04:19:11 2019 From: Pavlech.Juraj at azd.cz (Pavlech Juraj) Date: Tue, 19 Mar 2019 08:19:11 +0000 Subject: [CDash] Branch coverage percentage Message-ID: <1552983551780.15330@azd.cz> Hi, I added columns for gcov branch coverage to the coverageTable, it contains "branch percentage" column and "branches not covered" column , are you willing to make change like this ? I would like to hear your opinion. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cdash2.7.PNG Type: image/png Size: 78842 bytes Desc: cdash2.7.PNG URL: From sean at rogue-research.com Wed Mar 20 14:32:01 2019 From: sean at rogue-research.com (Sean McBride) Date: Wed, 20 Mar 2019 14:32:01 -0400 Subject: [CDash] CDash v2.6 released In-Reply-To: References: Message-ID: <20190320183201.1981758447@mail.rogue-research.com> On Tue, 20 Nov 2018 10:31:37 -0500, Zack Galbreath said: >https://github.com/Kitware/CDash/releases/tag/v2.6.0 Yet this page: says "The current stable CDash release is 2.4.0". Sean From zack.galbreath at kitware.com Thu Mar 21 09:38:12 2019 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Thu, 21 Mar 2019 09:38:12 -0400 Subject: [CDash] CDash v2.6 released In-Reply-To: <20190320183201.1981758447@mail.rogue-research.com> References: <20190320183201.1981758447@mail.rogue-research.com> Message-ID: Thanks for pointing this out, Sean. I updated the download page for v2.6. On Wed, Mar 20, 2019 at 2:32 PM Sean McBride wrote: > On Tue, 20 Nov 2018 10:31:37 -0500, Zack Galbreath said: > > >https://github.com/Kitware/CDash/releases/tag/v2.6.0 > > Yet this page: > > > says "The current stable CDash release is 2.4.0". > > Sean > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Thu Mar 21 09:49:14 2019 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Thu, 21 Mar 2019 09:49:14 -0400 Subject: [CDash] LDAP Authentication Issues In-Reply-To: <8fad53c13575444f812632c2edac3ddf@EXCHCS31.ornl.gov> References: <8fad53c13575444f812632c2edac3ddf@EXCHCS31.ornl.gov> Message-ID: On Wed, Mar 6, 2019 at 1:58 PM Martin, Mark via CDash < cdash at public.kitware.com> wrote: > Hello, > > > > I?ve established a CDash and have successfully authenticated, via database > authentication, the original admin user. However, I am experiencing > difficulty authenticating other users via LDAP. My LDAP configuration, > generally speaking, looks like this: > > > > $CDASH_USE_LDAP = ?1?; > > $CDASH_LDAP_HOSTNAME = ?myldapserver.mydomain.com?; > > $CDASH_LDAP_BASEDN = ?ou=Users,dc=mydc,dc=mydc2?; > > $CDASH_LDAP_PROTOCOL_VERSION = ?3?; > > > > I have concern that CDash may not be able to connect via ldaps:// > myldapserver.mydomain.com/. > > > > I am experiencing a login screen that just spins (loading) for ~3 minutes > before refreshing the login screen. No error messages are being generated > in the cdash.log file and no error messages are being displayed in the UI. > > > > Does anyone have any thoughts or advice on how I should proceed? > I can't say I've seen this behavior before. Without a publicly visible reproducer, the best I can suggest is debugging by print statement. Here is where the relevant code for LDAP authentication lives . And here's an example of how to write to cdash.log: add_log('this is me writing to the log file', 'ldapAuth checkpoint #1', LOG_WARNING); Good luck! Please let us know if you discover any juicy error messages. -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Thu Mar 21 09:55:21 2019 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Thu, 21 Mar 2019 09:55:21 -0400 Subject: [CDash] Database schema doesn't match the version of CDash In-Reply-To: <28db1225-2540-5c85-0ab1-9ef952b910a8@c-s.fr> References: <28db1225-2540-5c85-0ab1-9ef952b910a8@c-s.fr> Message-ID: On Fri, Mar 8, 2019 at 5:20 AM S?bastien Dinot wrote: > Dear all, > > As explained in my comment of issue #780 on Github > , I > have a problem when updating the database schema. > > I tried to migrate the dashboard of Orfeo Toolbox > from CDash 2.2.3 to CDash 2.6.0. After > installing the sources of version 2.6.0 and following the instructions > given on the "Upgrading CDash > " page, I > visited the CDash maintenance page. I clicked a first time on the "Upgrade > CDash" button and the patches for the version 2.4 were applied. I then > clicked a second time and the following messages were displayed: > > Upgrading tables: > Applying 2.8 patches: > > CDash Upgrade Successful. > > As far as I know, the version 2.8 doesn't exist yet. So, this message is > surprising and, indeed, the following message still appears on the home > page: > > The current database schema doesn't match the version of CDash you are > running, upgrade your database structure in the Administration/CDash > maintenance panel of CDash. > > What is the best way to correct this problem? > Thanks for the nudge. Here's what I think is going on: https://github.com/Kitware/CDash/issues/780#issuecomment-475237470 tl;dr: run UPDATE version SET minor = 4; and then click the "Upgrade CDash" button again -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Thu Mar 21 10:00:51 2019 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Thu, 21 Mar 2019 10:00:51 -0400 Subject: [CDash] Branch coverage percentage In-Reply-To: <1552983551780.15330@azd.cz> References: <1552983551780.15330@azd.cz> Message-ID: On Tue, Mar 19, 2019 at 4:19 AM Pavlech Juraj wrote: > > Hi, > > I added columns for gcov branch coverage to the coverageTable, it contains > "branch percentage" column and "branches not covered" column , are you > willing to make change like this ? > Looks like a good improvement to me. Thanks for working on this! -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuck.atkins at kitware.com Mon Mar 25 11:22:09 2019 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Mon, 25 Mar 2019 11:22:09 -0400 Subject: [CDash] LDAP Authentication Issues In-Reply-To: References: <8fad53c13575444f812632c2edac3ddf@EXCHCS31.ornl.gov> Message-ID: It may be possible that there's a failure in authenticating the ssl cert of your domain controller. Try adding the domain controller's public cert to your system's ssl trust store (how to do that is different for each linux distribution and ssl implementation ---------- Chuck Atkins Staff R&D Engineer, Scientific Computing Kitware, Inc. On Thu, Mar 21, 2019 at 9:49 AM Zack Galbreath via CDash < cdash at public.kitware.com> wrote: > On Wed, Mar 6, 2019 at 1:58 PM Martin, Mark via CDash < > cdash at public.kitware.com> wrote: > >> Hello, >> >> >> >> I?ve established a CDash and have successfully authenticated, via >> database authentication, the original admin user. However, I am >> experiencing difficulty authenticating other users via LDAP. My LDAP >> configuration, generally speaking, looks like this: >> >> >> >> $CDASH_USE_LDAP = ?1?; >> >> $CDASH_LDAP_HOSTNAME = ?myldapserver.mydomain.com?; >> >> $CDASH_LDAP_BASEDN = ?ou=Users,dc=mydc,dc=mydc2?; >> >> $CDASH_LDAP_PROTOCOL_VERSION = ?3?; >> >> >> >> I have concern that CDash may not be able to connect via ldaps:// >> myldapserver.mydomain.com/. >> >> >> >> I am experiencing a login screen that just spins (loading) for ~3 minutes >> before refreshing the login screen. No error messages are being generated >> in the cdash.log file and no error messages are being displayed in the UI. >> >> >> >> Does anyone have any thoughts or advice on how I should proceed? >> > > I can't say I've seen this behavior before. Without a publicly visible > reproducer, the best I can suggest is debugging by print statement. Here > is where the relevant code for LDAP authentication lives > . > And here's an example of how to write to cdash.log: > > add_log('this is me writing to the log file', 'ldapAuth checkpoint #1', > LOG_WARNING); > > Good luck! Please let us know if you discover any juicy error messages. > _______________________________________________ > CDash mailing list > CDash at public.kitware.com > https://public.kitware.com/mailman/listinfo/cdash > -------------- next part -------------- An HTML attachment was scrubbed... URL: From christian.morales.vega at gmail.com Mon Mar 4 09:03:15 2019 From: christian.morales.vega at gmail.com (Cristian Morales Vega) Date: Mon, 4 Mar 2019 09:03:15 +0000 Subject: [CDash] The "Bug Tracker" link in www.cdash.org/ is dead Message-ID: https://www.cdash.org/ "Bug Tracker" section points to either https://public.kitware.com/Bug/view_all_bug_page.php https://public.kitware.com/Bug/set_project.php?ref=view_all_set.php&project_id=23 Depending on whether you go first through https://www.cdash.org/developer-tools/. Both links are dead. FWIW I notice this because I wanted to open an issue for the CDash part of https://gitlab.kitware.com/cmake/cmake/issues/19003 i.e. there doesn't seem to be a way to have a "Dynamic Analysis" of a single "build" with two different "Checkers" (e.g. AddressSanitizer and UndefinedBehaviorSanitizer). From zack.galbreath at kitware.com Mon Mar 4 14:47:20 2019 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Mon, 4 Mar 2019 09:47:20 -0500 Subject: [CDash] The "Bug Tracker" link in www.cdash.org/ is dead In-Reply-To: References: Message-ID: On Mon, Mar 4, 2019 at 4:03 AM Cristian Morales Vega < christian.morales.vega at gmail.com> wrote: > https://www.cdash.org/ "Bug Tracker" section points to either > > https://public.kitware.com/Bug/view_all_bug_page.php > > https://public.kitware.com/Bug/set_project.php?ref=view_all_set.php&project_id=23 > > Depending on whether you go first through > https://www.cdash.org/developer-tools/. Both links are dead. > Thanks for letting us know. This should now point to the correct location. https://github.com/Kitware/CDash/issues -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Mon Mar 4 18:05:37 2019 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Mon, 4 Mar 2019 13:05:37 -0500 Subject: [CDash] Submitted "files" presentation In-Reply-To: References: Message-ID: On Tue, Feb 26, 2019 at 11:57 AM Cristian Morales Vega < christian.morales.vega at gmail.com> wrote: > On Tue, 26 Feb 2019 at 16:07, Cristian Morales Vega > wrote: > > ctest_submit() let's you submit PARTS, but also FILES. I have > > submitted a file with the output of "llvm-cov" with Source-based Code > > Coverage. I know CDash only supports gcov coverage right now, I don't > > expect to get full support for it. But I was hoping to be able to > > access the submitted file somehow from the CDash web view, linked > > somehow to the build. Maybe some "Extra files" section or something. > > I have actually managed to get what I wanted with ctest_upload(). Not > really sure what's supposed to be the difference, though. > I'm glad you figured out how to upload your file to CDash. In my experience, `ctest_submit(FILES ...)` is mostly used for manually submitting CTest XML files that have been generated previously. As you discovered, `ctest_upload` allows you to associate arbitrary files or URLs with your build. -------------- next part -------------- An HTML attachment was scrubbed... URL: From christian.morales.vega at gmail.com Mon Mar 4 20:06:25 2019 From: christian.morales.vega at gmail.com (Cristian Morales Vega) Date: Mon, 4 Mar 2019 20:06:25 +0000 Subject: [CDash] Submitted "files" presentation In-Reply-To: References: Message-ID: On Mon, 4 Mar 2019 at 18:05, Zack Galbreath wrote: > > On Tue, Feb 26, 2019 at 11:57 AM Cristian Morales Vega wrote: >> >> On Tue, 26 Feb 2019 at 16:07, Cristian Morales Vega >> wrote: >> > ctest_submit() let's you submit PARTS, but also FILES. I have >> > submitted a file with the output of "llvm-cov" with Source-based Code >> > Coverage. I know CDash only supports gcov coverage right now, I don't >> > expect to get full support for it. But I was hoping to be able to >> > access the submitted file somehow from the CDash web view, linked >> > somehow to the build. Maybe some "Extra files" section or something. >> >> I have actually managed to get what I wanted with ctest_upload(). Not >> really sure what's supposed to be the difference, though. > > > > I'm glad you figured out how to upload your file to CDash. > > In my experience, `ctest_submit(FILES ...)` is mostly used for manually submitting CTest XML files that have been generated previously. > > As you discovered, `ctest_upload` allows you to associate arbitrary files or URLs with your build. I have yet to try, but I'm now wondering what's the difference between the "Notes", "ExtraFiles" and "Upload" "PARTS". Notice that CTEST_NOTES_FILES and CTEST_EXTRA_SUBMIT_FILES don't appear in https://cmake.org/cmake/help/latest/manual/cmake-variables.7.html#variables-for-ctest. About "ctest_submit(FILES ...)". I have seen that https://blog.kitware.com/wp-content/uploads/2016/02/subproject_coverage_example.tar.gz from https://blog.kitware.com/additional-coverage-features-in-cdash/ does use it to send a Project.xml to create subprojects. But I have not seen that documented elsewhere and now I'm asking myself what other magic xml types can I send to do magic stuff... not curious enough yet to learn PHP, though :-) From martinma at ornl.gov Wed Mar 6 18:49:17 2019 From: martinma at ornl.gov (Martin, Mark) Date: Wed, 6 Mar 2019 18:49:17 +0000 Subject: [CDash] LDAP Authentication Issues Message-ID: <8fad53c13575444f812632c2edac3ddf@EXCHCS31.ornl.gov> Hello, I've established a CDash and have successfully authenticated, via database authentication, the original admin user. However, I am experiencing difficulty authenticating other users via LDAP. My LDAP configuration, generally speaking, looks like this: $CDASH_USE_LDAP = '1'; $CDASH_LDAP_HOSTNAME = 'myldapserver.mydomain.com'; $CDASH_LDAP_BASEDN = 'ou=Users,dc=mydc,dc=mydc2'; $CDASH_LDAP_PROTOCOL_VERSION = '3'; I have concern that CDash may not be able to connect via ldaps://myldapserver.mydomain.com/. I am experiencing a login screen that just spins (loading) for ~3 minutes before refreshing the login screen. No error messages are being generated in the cdash.log file and no error messages are being displayed in the UI. Does anyone have any thoughts or advice on how I should proceed? Best regards, -Mark -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Wed Mar 6 19:08:31 2019 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Wed, 6 Mar 2019 14:08:31 -0500 Subject: [CDash] Branch Coverage with GCov In-Reply-To: References: Message-ID: On Mon, Feb 25, 2019 at 12:54 PM Cristian Morales Vega < christian.morales.vega at gmail.com> wrote: > I'm wondering why the script uses ctest_coverage_collect_gcov() instead of > ctest_coverage() > When we implemented branch coverage in CDash, we made the design decision to let CDash handle the parsing. Previously coverage data was parsed by CTest (generating Coverage.xml and CoverageLog.xml) and then uploaded to CDash. With this new approach we now upload the .gcov files directly to CDash and parse them server-side instead. As to why this isn't working for you, I'm not sure. Do you see the uploaded gcov.tar file in your backup/ directory on the CDash server? -------------- next part -------------- An HTML attachment was scrubbed... URL: From christian.morales.vega at gmail.com Wed Mar 6 19:24:53 2019 From: christian.morales.vega at gmail.com (Cristian Morales Vega) Date: Wed, 6 Mar 2019 19:24:53 +0000 Subject: [CDash] Branch Coverage with GCov In-Reply-To: References: Message-ID: On Wed, 6 Mar 2019 at 19:08, Zack Galbreath wrote: > > On Mon, Feb 25, 2019 at 12:54 PM Cristian Morales Vega wrote: >> >> I'm wondering why the script uses ctest_coverage_collect_gcov() instead of ctest_coverage() > > > When we implemented branch coverage in CDash, we made the design decision to let CDash handle the parsing. Previously coverage data was parsed by CTest (generating Coverage.xml and CoverageLog.xml) and then uploaded to CDash. With this new approach we now upload the .gcov files directly to CDash and parse them server-side instead. > > As to why this isn't working for you, I'm not sure. Do you see the uploaded gcov.tar file in your backup/ directory on the CDash server? Knowing it's only supposed to work with ctest_coverage_collect_gcov() I will look further tomorrow. Thanks. But does this mean ctest_coverage() is deprecated and ctest_coverage_collect_gcov() is a strict superset? While reading the docs I got the impression ctest_coverage() is *the* way, with ctest_coverage_collect_gcov() something you notice while reading about something else, not too clear why it does exist. From sebastien.dinot at c-s.fr Fri Mar 8 10:07:48 2019 From: sebastien.dinot at c-s.fr (=?UTF-8?Q?S=c3=a9bastien_Dinot?=) Date: Fri, 8 Mar 2019 11:07:48 +0100 Subject: [CDash] Database schema doesn't match the version of CDash Message-ID: <28db1225-2540-5c85-0ab1-9ef952b910a8@c-s.fr> Dear all, As explained in my comment of issue #780 on Github , I have a problem when updating the database schema. I tried to migrate the dashboard of Orfeo Toolbox from CDash 2.2.3 to CDash 2.6.0. After installing the sources of version 2.6.0 and following the instructions given on the "Upgrading CDash " page, I visited the CDash maintenance page. I clicked a first time on the "Upgrade CDash" button and the patches for the version 2.4 were applied. I then clicked a second time and the following messages were displayed: Upgrading tables: Applying 2.8 patches: CDash Upgrade Successful. As far as I know, the version 2.8 doesn't exist yet. So, this message is surprising and, indeed, the following message still appears on the home page: The current database schema doesn't match the version of CDash you are running, upgrade your database structure in the Administration/CDash maintenance panel of CDash. What is the best way to correct this problem? Thank you in advance, S?bastien -------------- next part -------------- An HTML attachment was scrubbed... URL: From Pavlech.Juraj at azd.cz Tue Mar 19 08:19:11 2019 From: Pavlech.Juraj at azd.cz (Pavlech Juraj) Date: Tue, 19 Mar 2019 08:19:11 +0000 Subject: [CDash] Branch coverage percentage Message-ID: <1552983551780.15330@azd.cz> Hi, I added columns for gcov branch coverage to the coverageTable, it contains "branch percentage" column and "branches not covered" column , are you willing to make change like this ? I would like to hear your opinion. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cdash2.7.PNG Type: image/png Size: 78842 bytes Desc: cdash2.7.PNG URL: From sean at rogue-research.com Wed Mar 20 18:32:01 2019 From: sean at rogue-research.com (Sean McBride) Date: Wed, 20 Mar 2019 14:32:01 -0400 Subject: [CDash] CDash v2.6 released In-Reply-To: References: Message-ID: <20190320183201.1981758447@mail.rogue-research.com> On Tue, 20 Nov 2018 10:31:37 -0500, Zack Galbreath said: >https://github.com/Kitware/CDash/releases/tag/v2.6.0 Yet this page: says "The current stable CDash release is 2.4.0". Sean From zack.galbreath at kitware.com Thu Mar 21 13:38:12 2019 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Thu, 21 Mar 2019 09:38:12 -0400 Subject: [CDash] CDash v2.6 released In-Reply-To: <20190320183201.1981758447@mail.rogue-research.com> References: <20190320183201.1981758447@mail.rogue-research.com> Message-ID: Thanks for pointing this out, Sean. I updated the download page for v2.6. On Wed, Mar 20, 2019 at 2:32 PM Sean McBride wrote: > On Tue, 20 Nov 2018 10:31:37 -0500, Zack Galbreath said: > > >https://github.com/Kitware/CDash/releases/tag/v2.6.0 > > Yet this page: > > > says "The current stable CDash release is 2.4.0". > > Sean > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Thu Mar 21 13:49:14 2019 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Thu, 21 Mar 2019 09:49:14 -0400 Subject: [CDash] LDAP Authentication Issues In-Reply-To: <8fad53c13575444f812632c2edac3ddf@EXCHCS31.ornl.gov> References: <8fad53c13575444f812632c2edac3ddf@EXCHCS31.ornl.gov> Message-ID: On Wed, Mar 6, 2019 at 1:58 PM Martin, Mark via CDash < cdash at public.kitware.com> wrote: > Hello, > > > > I?ve established a CDash and have successfully authenticated, via database > authentication, the original admin user. However, I am experiencing > difficulty authenticating other users via LDAP. My LDAP configuration, > generally speaking, looks like this: > > > > $CDASH_USE_LDAP = ?1?; > > $CDASH_LDAP_HOSTNAME = ?myldapserver.mydomain.com?; > > $CDASH_LDAP_BASEDN = ?ou=Users,dc=mydc,dc=mydc2?; > > $CDASH_LDAP_PROTOCOL_VERSION = ?3?; > > > > I have concern that CDash may not be able to connect via ldaps:// > myldapserver.mydomain.com/. > > > > I am experiencing a login screen that just spins (loading) for ~3 minutes > before refreshing the login screen. No error messages are being generated > in the cdash.log file and no error messages are being displayed in the UI. > > > > Does anyone have any thoughts or advice on how I should proceed? > I can't say I've seen this behavior before. Without a publicly visible reproducer, the best I can suggest is debugging by print statement. Here is where the relevant code for LDAP authentication lives . And here's an example of how to write to cdash.log: add_log('this is me writing to the log file', 'ldapAuth checkpoint #1', LOG_WARNING); Good luck! Please let us know if you discover any juicy error messages. -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Thu Mar 21 13:55:21 2019 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Thu, 21 Mar 2019 09:55:21 -0400 Subject: [CDash] Database schema doesn't match the version of CDash In-Reply-To: <28db1225-2540-5c85-0ab1-9ef952b910a8@c-s.fr> References: <28db1225-2540-5c85-0ab1-9ef952b910a8@c-s.fr> Message-ID: On Fri, Mar 8, 2019 at 5:20 AM S?bastien Dinot wrote: > Dear all, > > As explained in my comment of issue #780 on Github > , I > have a problem when updating the database schema. > > I tried to migrate the dashboard of Orfeo Toolbox > from CDash 2.2.3 to CDash 2.6.0. After > installing the sources of version 2.6.0 and following the instructions > given on the "Upgrading CDash > " page, I > visited the CDash maintenance page. I clicked a first time on the "Upgrade > CDash" button and the patches for the version 2.4 were applied. I then > clicked a second time and the following messages were displayed: > > Upgrading tables: > Applying 2.8 patches: > > CDash Upgrade Successful. > > As far as I know, the version 2.8 doesn't exist yet. So, this message is > surprising and, indeed, the following message still appears on the home > page: > > The current database schema doesn't match the version of CDash you are > running, upgrade your database structure in the Administration/CDash > maintenance panel of CDash. > > What is the best way to correct this problem? > Thanks for the nudge. Here's what I think is going on: https://github.com/Kitware/CDash/issues/780#issuecomment-475237470 tl;dr: run UPDATE version SET minor = 4; and then click the "Upgrade CDash" button again -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Thu Mar 21 14:00:51 2019 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Thu, 21 Mar 2019 10:00:51 -0400 Subject: [CDash] Branch coverage percentage In-Reply-To: <1552983551780.15330@azd.cz> References: <1552983551780.15330@azd.cz> Message-ID: On Tue, Mar 19, 2019 at 4:19 AM Pavlech Juraj wrote: > > Hi, > > I added columns for gcov branch coverage to the coverageTable, it contains > "branch percentage" column and "branches not covered" column , are you > willing to make change like this ? > Looks like a good improvement to me. Thanks for working on this! -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuck.atkins at kitware.com Mon Mar 25 15:22:09 2019 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Mon, 25 Mar 2019 11:22:09 -0400 Subject: [CDash] LDAP Authentication Issues In-Reply-To: References: <8fad53c13575444f812632c2edac3ddf@EXCHCS31.ornl.gov> Message-ID: It may be possible that there's a failure in authenticating the ssl cert of your domain controller. Try adding the domain controller's public cert to your system's ssl trust store (how to do that is different for each linux distribution and ssl implementation ---------- Chuck Atkins Staff R&D Engineer, Scientific Computing Kitware, Inc. On Thu, Mar 21, 2019 at 9:49 AM Zack Galbreath via CDash < cdash at public.kitware.com> wrote: > On Wed, Mar 6, 2019 at 1:58 PM Martin, Mark via CDash < > cdash at public.kitware.com> wrote: > >> Hello, >> >> >> >> I?ve established a CDash and have successfully authenticated, via >> database authentication, the original admin user. However, I am >> experiencing difficulty authenticating other users via LDAP. My LDAP >> configuration, generally speaking, looks like this: >> >> >> >> $CDASH_USE_LDAP = ?1?; >> >> $CDASH_LDAP_HOSTNAME = ?myldapserver.mydomain.com?; >> >> $CDASH_LDAP_BASEDN = ?ou=Users,dc=mydc,dc=mydc2?; >> >> $CDASH_LDAP_PROTOCOL_VERSION = ?3?; >> >> >> >> I have concern that CDash may not be able to connect via ldaps:// >> myldapserver.mydomain.com/. >> >> >> >> I am experiencing a login screen that just spins (loading) for ~3 minutes >> before refreshing the login screen. No error messages are being generated >> in the cdash.log file and no error messages are being displayed in the UI. >> >> >> >> Does anyone have any thoughts or advice on how I should proceed? >> > > I can't say I've seen this behavior before. Without a publicly visible > reproducer, the best I can suggest is debugging by print statement. Here > is where the relevant code for LDAP authentication lives > . > And here's an example of how to write to cdash.log: > > add_log('this is me writing to the log file', 'ldapAuth checkpoint #1', > LOG_WARNING); > > Good luck! Please let us know if you discover any juicy error messages. > _______________________________________________ > CDash mailing list > CDash at public.kitware.com > https://public.kitware.com/mailman/listinfo/cdash > -------------- next part -------------- An HTML attachment was scrubbed... URL: From christian.morales.vega at gmail.com Mon Mar 4 09:03:15 2019 From: christian.morales.vega at gmail.com (Cristian Morales Vega) Date: Mon, 4 Mar 2019 09:03:15 +0000 Subject: [CDash] The "Bug Tracker" link in www.cdash.org/ is dead Message-ID: https://www.cdash.org/ "Bug Tracker" section points to either https://public.kitware.com/Bug/view_all_bug_page.php https://public.kitware.com/Bug/set_project.php?ref=view_all_set.php&project_id=23 Depending on whether you go first through https://www.cdash.org/developer-tools/. Both links are dead. FWIW I notice this because I wanted to open an issue for the CDash part of https://gitlab.kitware.com/cmake/cmake/issues/19003 i.e. there doesn't seem to be a way to have a "Dynamic Analysis" of a single "build" with two different "Checkers" (e.g. AddressSanitizer and UndefinedBehaviorSanitizer). From zack.galbreath at kitware.com Mon Mar 4 14:47:20 2019 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Mon, 4 Mar 2019 09:47:20 -0500 Subject: [CDash] The "Bug Tracker" link in www.cdash.org/ is dead In-Reply-To: References: Message-ID: On Mon, Mar 4, 2019 at 4:03 AM Cristian Morales Vega < christian.morales.vega at gmail.com> wrote: > https://www.cdash.org/ "Bug Tracker" section points to either > > https://public.kitware.com/Bug/view_all_bug_page.php > > https://public.kitware.com/Bug/set_project.php?ref=view_all_set.php&project_id=23 > > Depending on whether you go first through > https://www.cdash.org/developer-tools/. Both links are dead. > Thanks for letting us know. This should now point to the correct location. https://github.com/Kitware/CDash/issues -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Mon Mar 4 18:05:37 2019 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Mon, 4 Mar 2019 13:05:37 -0500 Subject: [CDash] Submitted "files" presentation In-Reply-To: References: Message-ID: On Tue, Feb 26, 2019 at 11:57 AM Cristian Morales Vega < christian.morales.vega at gmail.com> wrote: > On Tue, 26 Feb 2019 at 16:07, Cristian Morales Vega > wrote: > > ctest_submit() let's you submit PARTS, but also FILES. I have > > submitted a file with the output of "llvm-cov" with Source-based Code > > Coverage. I know CDash only supports gcov coverage right now, I don't > > expect to get full support for it. But I was hoping to be able to > > access the submitted file somehow from the CDash web view, linked > > somehow to the build. Maybe some "Extra files" section or something. > > I have actually managed to get what I wanted with ctest_upload(). Not > really sure what's supposed to be the difference, though. > I'm glad you figured out how to upload your file to CDash. In my experience, `ctest_submit(FILES ...)` is mostly used for manually submitting CTest XML files that have been generated previously. As you discovered, `ctest_upload` allows you to associate arbitrary files or URLs with your build. -------------- next part -------------- An HTML attachment was scrubbed... URL: From christian.morales.vega at gmail.com Mon Mar 4 20:06:25 2019 From: christian.morales.vega at gmail.com (Cristian Morales Vega) Date: Mon, 4 Mar 2019 20:06:25 +0000 Subject: [CDash] Submitted "files" presentation In-Reply-To: References: Message-ID: On Mon, 4 Mar 2019 at 18:05, Zack Galbreath wrote: > > On Tue, Feb 26, 2019 at 11:57 AM Cristian Morales Vega wrote: >> >> On Tue, 26 Feb 2019 at 16:07, Cristian Morales Vega >> wrote: >> > ctest_submit() let's you submit PARTS, but also FILES. I have >> > submitted a file with the output of "llvm-cov" with Source-based Code >> > Coverage. I know CDash only supports gcov coverage right now, I don't >> > expect to get full support for it. But I was hoping to be able to >> > access the submitted file somehow from the CDash web view, linked >> > somehow to the build. Maybe some "Extra files" section or something. >> >> I have actually managed to get what I wanted with ctest_upload(). Not >> really sure what's supposed to be the difference, though. > > > > I'm glad you figured out how to upload your file to CDash. > > In my experience, `ctest_submit(FILES ...)` is mostly used for manually submitting CTest XML files that have been generated previously. > > As you discovered, `ctest_upload` allows you to associate arbitrary files or URLs with your build. I have yet to try, but I'm now wondering what's the difference between the "Notes", "ExtraFiles" and "Upload" "PARTS". Notice that CTEST_NOTES_FILES and CTEST_EXTRA_SUBMIT_FILES don't appear in https://cmake.org/cmake/help/latest/manual/cmake-variables.7.html#variables-for-ctest. About "ctest_submit(FILES ...)". I have seen that https://blog.kitware.com/wp-content/uploads/2016/02/subproject_coverage_example.tar.gz from https://blog.kitware.com/additional-coverage-features-in-cdash/ does use it to send a Project.xml to create subprojects. But I have not seen that documented elsewhere and now I'm asking myself what other magic xml types can I send to do magic stuff... not curious enough yet to learn PHP, though :-) From martinma at ornl.gov Wed Mar 6 18:49:17 2019 From: martinma at ornl.gov (Martin, Mark) Date: Wed, 6 Mar 2019 18:49:17 +0000 Subject: [CDash] LDAP Authentication Issues Message-ID: <8fad53c13575444f812632c2edac3ddf@EXCHCS31.ornl.gov> Hello, I've established a CDash and have successfully authenticated, via database authentication, the original admin user. However, I am experiencing difficulty authenticating other users via LDAP. My LDAP configuration, generally speaking, looks like this: $CDASH_USE_LDAP = '1'; $CDASH_LDAP_HOSTNAME = 'myldapserver.mydomain.com'; $CDASH_LDAP_BASEDN = 'ou=Users,dc=mydc,dc=mydc2'; $CDASH_LDAP_PROTOCOL_VERSION = '3'; I have concern that CDash may not be able to connect via ldaps://myldapserver.mydomain.com/. I am experiencing a login screen that just spins (loading) for ~3 minutes before refreshing the login screen. No error messages are being generated in the cdash.log file and no error messages are being displayed in the UI. Does anyone have any thoughts or advice on how I should proceed? Best regards, -Mark -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Wed Mar 6 19:08:31 2019 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Wed, 6 Mar 2019 14:08:31 -0500 Subject: [CDash] Branch Coverage with GCov In-Reply-To: References: Message-ID: On Mon, Feb 25, 2019 at 12:54 PM Cristian Morales Vega < christian.morales.vega at gmail.com> wrote: > I'm wondering why the script uses ctest_coverage_collect_gcov() instead of > ctest_coverage() > When we implemented branch coverage in CDash, we made the design decision to let CDash handle the parsing. Previously coverage data was parsed by CTest (generating Coverage.xml and CoverageLog.xml) and then uploaded to CDash. With this new approach we now upload the .gcov files directly to CDash and parse them server-side instead. As to why this isn't working for you, I'm not sure. Do you see the uploaded gcov.tar file in your backup/ directory on the CDash server? -------------- next part -------------- An HTML attachment was scrubbed... URL: From christian.morales.vega at gmail.com Wed Mar 6 19:24:53 2019 From: christian.morales.vega at gmail.com (Cristian Morales Vega) Date: Wed, 6 Mar 2019 19:24:53 +0000 Subject: [CDash] Branch Coverage with GCov In-Reply-To: References: Message-ID: On Wed, 6 Mar 2019 at 19:08, Zack Galbreath wrote: > > On Mon, Feb 25, 2019 at 12:54 PM Cristian Morales Vega wrote: >> >> I'm wondering why the script uses ctest_coverage_collect_gcov() instead of ctest_coverage() > > > When we implemented branch coverage in CDash, we made the design decision to let CDash handle the parsing. Previously coverage data was parsed by CTest (generating Coverage.xml and CoverageLog.xml) and then uploaded to CDash. With this new approach we now upload the .gcov files directly to CDash and parse them server-side instead. > > As to why this isn't working for you, I'm not sure. Do you see the uploaded gcov.tar file in your backup/ directory on the CDash server? Knowing it's only supposed to work with ctest_coverage_collect_gcov() I will look further tomorrow. Thanks. But does this mean ctest_coverage() is deprecated and ctest_coverage_collect_gcov() is a strict superset? While reading the docs I got the impression ctest_coverage() is *the* way, with ctest_coverage_collect_gcov() something you notice while reading about something else, not too clear why it does exist. From sebastien.dinot at c-s.fr Fri Mar 8 10:07:48 2019 From: sebastien.dinot at c-s.fr (=?UTF-8?Q?S=c3=a9bastien_Dinot?=) Date: Fri, 8 Mar 2019 11:07:48 +0100 Subject: [CDash] Database schema doesn't match the version of CDash Message-ID: <28db1225-2540-5c85-0ab1-9ef952b910a8@c-s.fr> Dear all, As explained in my comment of issue #780 on Github , I have a problem when updating the database schema. I tried to migrate the dashboard of Orfeo Toolbox from CDash 2.2.3 to CDash 2.6.0. After installing the sources of version 2.6.0 and following the instructions given on the "Upgrading CDash " page, I visited the CDash maintenance page. I clicked a first time on the "Upgrade CDash" button and the patches for the version 2.4 were applied. I then clicked a second time and the following messages were displayed: Upgrading tables: Applying 2.8 patches: CDash Upgrade Successful. As far as I know, the version 2.8 doesn't exist yet. So, this message is surprising and, indeed, the following message still appears on the home page: The current database schema doesn't match the version of CDash you are running, upgrade your database structure in the Administration/CDash maintenance panel of CDash. What is the best way to correct this problem? Thank you in advance, S?bastien -------------- next part -------------- An HTML attachment was scrubbed... URL: From Pavlech.Juraj at azd.cz Tue Mar 19 08:19:11 2019 From: Pavlech.Juraj at azd.cz (Pavlech Juraj) Date: Tue, 19 Mar 2019 08:19:11 +0000 Subject: [CDash] Branch coverage percentage Message-ID: <1552983551780.15330@azd.cz> Hi, I added columns for gcov branch coverage to the coverageTable, it contains "branch percentage" column and "branches not covered" column , are you willing to make change like this ? I would like to hear your opinion. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cdash2.7.PNG Type: image/png Size: 78842 bytes Desc: cdash2.7.PNG URL: From sean at rogue-research.com Wed Mar 20 18:32:01 2019 From: sean at rogue-research.com (Sean McBride) Date: Wed, 20 Mar 2019 14:32:01 -0400 Subject: [CDash] CDash v2.6 released In-Reply-To: References: Message-ID: <20190320183201.1981758447@mail.rogue-research.com> On Tue, 20 Nov 2018 10:31:37 -0500, Zack Galbreath said: >https://github.com/Kitware/CDash/releases/tag/v2.6.0 Yet this page: says "The current stable CDash release is 2.4.0". Sean From zack.galbreath at kitware.com Thu Mar 21 13:38:12 2019 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Thu, 21 Mar 2019 09:38:12 -0400 Subject: [CDash] CDash v2.6 released In-Reply-To: <20190320183201.1981758447@mail.rogue-research.com> References: <20190320183201.1981758447@mail.rogue-research.com> Message-ID: Thanks for pointing this out, Sean. I updated the download page for v2.6. On Wed, Mar 20, 2019 at 2:32 PM Sean McBride wrote: > On Tue, 20 Nov 2018 10:31:37 -0500, Zack Galbreath said: > > >https://github.com/Kitware/CDash/releases/tag/v2.6.0 > > Yet this page: > > > says "The current stable CDash release is 2.4.0". > > Sean > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Thu Mar 21 13:49:14 2019 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Thu, 21 Mar 2019 09:49:14 -0400 Subject: [CDash] LDAP Authentication Issues In-Reply-To: <8fad53c13575444f812632c2edac3ddf@EXCHCS31.ornl.gov> References: <8fad53c13575444f812632c2edac3ddf@EXCHCS31.ornl.gov> Message-ID: On Wed, Mar 6, 2019 at 1:58 PM Martin, Mark via CDash < cdash at public.kitware.com> wrote: > Hello, > > > > I?ve established a CDash and have successfully authenticated, via database > authentication, the original admin user. However, I am experiencing > difficulty authenticating other users via LDAP. My LDAP configuration, > generally speaking, looks like this: > > > > $CDASH_USE_LDAP = ?1?; > > $CDASH_LDAP_HOSTNAME = ?myldapserver.mydomain.com?; > > $CDASH_LDAP_BASEDN = ?ou=Users,dc=mydc,dc=mydc2?; > > $CDASH_LDAP_PROTOCOL_VERSION = ?3?; > > > > I have concern that CDash may not be able to connect via ldaps:// > myldapserver.mydomain.com/. > > > > I am experiencing a login screen that just spins (loading) for ~3 minutes > before refreshing the login screen. No error messages are being generated > in the cdash.log file and no error messages are being displayed in the UI. > > > > Does anyone have any thoughts or advice on how I should proceed? > I can't say I've seen this behavior before. Without a publicly visible reproducer, the best I can suggest is debugging by print statement. Here is where the relevant code for LDAP authentication lives . And here's an example of how to write to cdash.log: add_log('this is me writing to the log file', 'ldapAuth checkpoint #1', LOG_WARNING); Good luck! Please let us know if you discover any juicy error messages. -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Thu Mar 21 13:55:21 2019 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Thu, 21 Mar 2019 09:55:21 -0400 Subject: [CDash] Database schema doesn't match the version of CDash In-Reply-To: <28db1225-2540-5c85-0ab1-9ef952b910a8@c-s.fr> References: <28db1225-2540-5c85-0ab1-9ef952b910a8@c-s.fr> Message-ID: On Fri, Mar 8, 2019 at 5:20 AM S?bastien Dinot wrote: > Dear all, > > As explained in my comment of issue #780 on Github > , I > have a problem when updating the database schema. > > I tried to migrate the dashboard of Orfeo Toolbox > from CDash 2.2.3 to CDash 2.6.0. After > installing the sources of version 2.6.0 and following the instructions > given on the "Upgrading CDash > " page, I > visited the CDash maintenance page. I clicked a first time on the "Upgrade > CDash" button and the patches for the version 2.4 were applied. I then > clicked a second time and the following messages were displayed: > > Upgrading tables: > Applying 2.8 patches: > > CDash Upgrade Successful. > > As far as I know, the version 2.8 doesn't exist yet. So, this message is > surprising and, indeed, the following message still appears on the home > page: > > The current database schema doesn't match the version of CDash you are > running, upgrade your database structure in the Administration/CDash > maintenance panel of CDash. > > What is the best way to correct this problem? > Thanks for the nudge. Here's what I think is going on: https://github.com/Kitware/CDash/issues/780#issuecomment-475237470 tl;dr: run UPDATE version SET minor = 4; and then click the "Upgrade CDash" button again -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Thu Mar 21 14:00:51 2019 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Thu, 21 Mar 2019 10:00:51 -0400 Subject: [CDash] Branch coverage percentage In-Reply-To: <1552983551780.15330@azd.cz> References: <1552983551780.15330@azd.cz> Message-ID: On Tue, Mar 19, 2019 at 4:19 AM Pavlech Juraj wrote: > > Hi, > > I added columns for gcov branch coverage to the coverageTable, it contains > "branch percentage" column and "branches not covered" column , are you > willing to make change like this ? > Looks like a good improvement to me. Thanks for working on this! -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuck.atkins at kitware.com Mon Mar 25 15:22:09 2019 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Mon, 25 Mar 2019 11:22:09 -0400 Subject: [CDash] LDAP Authentication Issues In-Reply-To: References: <8fad53c13575444f812632c2edac3ddf@EXCHCS31.ornl.gov> Message-ID: It may be possible that there's a failure in authenticating the ssl cert of your domain controller. Try adding the domain controller's public cert to your system's ssl trust store (how to do that is different for each linux distribution and ssl implementation ---------- Chuck Atkins Staff R&D Engineer, Scientific Computing Kitware, Inc. On Thu, Mar 21, 2019 at 9:49 AM Zack Galbreath via CDash < cdash at public.kitware.com> wrote: > On Wed, Mar 6, 2019 at 1:58 PM Martin, Mark via CDash < > cdash at public.kitware.com> wrote: > >> Hello, >> >> >> >> I?ve established a CDash and have successfully authenticated, via >> database authentication, the original admin user. However, I am >> experiencing difficulty authenticating other users via LDAP. My LDAP >> configuration, generally speaking, looks like this: >> >> >> >> $CDASH_USE_LDAP = ?1?; >> >> $CDASH_LDAP_HOSTNAME = ?myldapserver.mydomain.com?; >> >> $CDASH_LDAP_BASEDN = ?ou=Users,dc=mydc,dc=mydc2?; >> >> $CDASH_LDAP_PROTOCOL_VERSION = ?3?; >> >> >> >> I have concern that CDash may not be able to connect via ldaps:// >> myldapserver.mydomain.com/. >> >> >> >> I am experiencing a login screen that just spins (loading) for ~3 minutes >> before refreshing the login screen. No error messages are being generated >> in the cdash.log file and no error messages are being displayed in the UI. >> >> >> >> Does anyone have any thoughts or advice on how I should proceed? >> > > I can't say I've seen this behavior before. Without a publicly visible > reproducer, the best I can suggest is debugging by print statement. Here > is where the relevant code for LDAP authentication lives > . > And here's an example of how to write to cdash.log: > > add_log('this is me writing to the log file', 'ldapAuth checkpoint #1', > LOG_WARNING); > > Good luck! Please let us know if you discover any juicy error messages. > _______________________________________________ > CDash mailing list > CDash at public.kitware.com > https://public.kitware.com/mailman/listinfo/cdash > -------------- next part -------------- An HTML attachment was scrubbed... URL: