From bloring at lbl.gov Fri Oct 2 14:43:27 2015 From: bloring at lbl.gov (Burlen Loring) Date: Fri, 02 Oct 2015 11:43:27 -0700 Subject: [Cdash] cdash bug Message-ID: <560ED04F.1030709@lbl.gov> Hi All, Ever since we upgraded to cdash 2.2.2 the web display has been broken for tests that have multiple image diffs. We are now running 2.2.3 and still have the issue. The interactive image widget is only displayed for the first failure. It needs to be displayed for each failure. This can be reproduced using ctest with ParaView. Here is an experimental submission to ParaView dashboard illustrating the issue. There are 4 failures, but only one interactive widget displayed. https://open.cdash.org/testDetails.php?test=379396531&build=4043227 steps to reproduce in ParaView ctest: 1) find a test case that has multiple image diffs, I chose vtkSciberQuestCxx-MPI-TestVortexFilter because I know it has multiple tests 2) modify two or more of the baseline in an image editor to produce a failure 3) run the test and send it to the dashboard I filed a bug report, http://public.kitware.com/Bug/view.php?id=15764 This is a major obstacle in our transition to ctest, can you comment on plans to address it? Please let me know if there is a work around in the mean time. Thanks Burlen -------------- next part -------------- An HTML attachment was scrubbed... URL: From bloring at lbl.gov Wed Oct 7 10:14:17 2015 From: bloring at lbl.gov (Burlen Loring) Date: Wed, 7 Oct 2015 07:14:17 -0700 Subject: [Cdash] SQL error: SQL error encountered, query hidden. Message-ID: <561528B9.9010906@lbl.gov> Anyone know what this cdash error is about? It recently began appearing and results for some submissions are not displayed on the main page. *Error * reported on 2015-10-07 05:57:44 for build #6012 /(compute_test_difference): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:43 for build #6012 /(compute_test_difference): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:43 for build #6012 /(compute_test_difference): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:34 for build #6012 /(Label::InsertAssociation): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:31 for build #6012 /(Label::InsertAssociation): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:23 for build #6012 /(Label::InsertAssociation): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:23 for build #6012 /(Label::InsertAssociation): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:23 for build #6012 /(Label::InsertAssociation): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:23 for build #6012 /(Label::InsertAssociation): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:19 for build #6012 /(Label::InsertAssociation): SQL error: SQL error encountered, query hidden./ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: error.png Type: image/png Size: 4208 bytes Desc: not available URL: From zack.galbreath at kitware.com Wed Oct 7 10:30:10 2015 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Wed, 7 Oct 2015 10:30:10 -0400 Subject: [Cdash] SQL error: SQL error encountered, query hidden. In-Reply-To: <561528B9.9010906@lbl.gov> References: <561528B9.9010906@lbl.gov> Message-ID: Hi Burlen, On Wed, Oct 7, 2015 at 10:14 AM, Burlen Loring wrote: > Anyone know what this cdash error is about? It recently began appearing > and results for some submissions are not displayed on the main page. > These errors aren't familiar to me. If you have the permissions necessary to edit config.local.php, try temporarily setting $CDASH_PRODUCTION_MODE to false. This will show you the actual queries that are failing, rather than "query hidden". -------------- next part -------------- An HTML attachment was scrubbed... URL: From bloring at lbl.gov Sat Oct 10 17:32:16 2015 From: bloring at lbl.gov (Burlen Loring) Date: Sat, 10 Oct 2015 14:32:16 -0700 Subject: [Cdash] SQL error: SQL error encountered, query hidden. In-Reply-To: References: <561528B9.9010906@lbl.gov> Message-ID: <561983E0.6010207@lbl.gov> thanks Zack, output below. Also when I go to the page to show the list of failed tests there are 4 entries for each test. http://cdash.visit.lbl.gov/viewTest.php?onlyfailed&buildid=6045 Error Log *Error*reported on 2015-10-10 06:06:15 forbuild #6045 /(compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction/ *Error*reported on 2015-10-10 06:06:14 forbuild #6045 /(compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction/ *Error*reported on 2015-10-10 06:06:14 forbuild #6045 /(compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction/ *Error*reported on 2015-10-10 06:06:14 forbuild #6045 /(compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction/ *Error*reported on 2015-10-10 06:06:14 forbuild #6045 /(compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction/ *Error*reported on 2015-10-10 06:05:57 forbuild #6045 /(Label::InsertAssociation): SQL error: Duplicate entry '1-6045-2128329' for key 'PRIMARY'/ *Error*reported on 2015-10-10 06:05:55 forbuild #6045 /(Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2101676' for key 'PRIMARY'/ *Error*reported on 2015-10-10 06:05:55 forbuild #6045 /(Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2101678' for key 'PRIMARY'/ *Error*reported on 2015-10-10 06:05:55 forbuild #6045 /(Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2128322' for key 'PRIMARY'/ *Error*reported on 2015-10-10 06:05:55 forbuild #6045 /(Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2101680' for key 'PRIMARY'/ *Error*reported on 2015-10-10 06:05:55 forbuild #6045 /(Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2101683' for key 'PRIMARY'/ *Error*reported on 2015-10-10 06:05:53 forbuild #6045 /(Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2128292' for key 'PRIMARY'/ *Error*reported on 2015-10-10 06:05:53 forbuild #6045 /(Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2128302' for key 'PRIMARY'/ On 10/7/2015 7:30 AM, Zack Galbreath wrote: > Hi Burlen, > > On Wed, Oct 7, 2015 at 10:14 AM, Burlen Loring > wrote: > > Anyone know what this cdash error is about? It recently began > appearing and results for some submissions are not displayed on > the main page. > > > These errors aren't familiar to me. If you have the permissions > necessary to edit config.local.php, try temporarily setting > $CDASH_PRODUCTION_MODE to false. This will show you the actual > queries that are failing, rather than "query hidden". -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: error.png Type: image/png Size: 4208 bytes Desc: not available URL: From mike.jackson at bluequartz.net Thu Oct 15 09:40:27 2015 From: mike.jackson at bluequartz.net (Michael Jackson) Date: Thu, 15 Oct 2015 09:40:27 -0400 Subject: [Cdash] Server Down Message-ID: is my.cdash.org down? -- Mike Jackson From bill.hoffman at kitware.com Thu Oct 15 11:46:13 2015 From: bill.hoffman at kitware.com (Bill Hoffman) Date: Thu, 15 Oct 2015 11:46:13 -0400 Subject: [Cdash] Server Down In-Reply-To: References: Message-ID: <561FCA45.6080709@kitware.com> On 10/15/2015 9:40 AM, Michael Jackson wrote: > is my.cdash.org down? Yes, we are working on it. Thanks for the report. -- Bill Hoffman Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 bill.hoffman at kitware.com http://www.kitware.com 518 881-4905 (Direct) 518 371-3971 x105 Fax (518) 371-4573 From bloring at lbl.gov Thu Oct 15 19:01:46 2015 From: bloring at lbl.gov (Burlen Loring) Date: Thu, 15 Oct 2015 16:01:46 -0700 Subject: [Cdash] SQL error: SQL error encountered, query hidden. In-Reply-To: <561983E0.6010207@lbl.gov> References: <561528B9.9010906@lbl.gov> <561983E0.6010207@lbl.gov> Message-ID: <5620305A.7070908@lbl.gov> OK, so our disk was full. that may have caused some of this. we will see tonight if the error go away. One issue is that cdash had submission xml files starting from over a year ago until the disk got full in ./backup. in my config.loval.php I have : CDASH_BACKUP_TIMEFRAME=48 cdash is supposed to delete them after 48 hours right? any idea why it might not be deleted? On 10/10/2015 02:32 PM, Burlen Loring wrote: > thanks Zack, output below. Also when I go to the page to show the list > of failed tests there are 4 entries for each test. > http://cdash.visit.lbl.gov/viewTest.php?onlyfailed&buildid=6045 > > > Error Log > > *Error*reported on 2015-10-10 06:06:15 forbuild #6045 > > /(compute_test_difference): SQL error: Deadlock found when trying to > get lock; try restarting transaction/ > > *Error*reported on 2015-10-10 06:06:14 forbuild #6045 > > /(compute_test_difference): SQL error: Deadlock found when trying to > get lock; try restarting transaction/ > > *Error*reported on 2015-10-10 06:06:14 forbuild #6045 > > /(compute_test_difference): SQL error: Deadlock found when trying to > get lock; try restarting transaction/ > > *Error*reported on 2015-10-10 06:06:14 forbuild #6045 > > /(compute_test_difference): SQL error: Deadlock found when trying to > get lock; try restarting transaction/ > > *Error*reported on 2015-10-10 06:06:14 forbuild #6045 > > /(compute_test_difference): SQL error: Deadlock found when trying to > get lock; try restarting transaction/ > > *Error*reported on 2015-10-10 06:05:57 forbuild #6045 > > /(Label::InsertAssociation): SQL error: Duplicate entry > '1-6045-2128329' for key 'PRIMARY'/ > > *Error*reported on 2015-10-10 06:05:55 forbuild #6045 > > /(Label::InsertAssociation): SQL error: Duplicate entry > '2-6045-2101676' for key 'PRIMARY'/ > > *Error*reported on 2015-10-10 06:05:55 forbuild #6045 > > /(Label::InsertAssociation): SQL error: Duplicate entry > '2-6045-2101678' for key 'PRIMARY'/ > > *Error*reported on 2015-10-10 06:05:55 forbuild #6045 > > /(Label::InsertAssociation): SQL error: Duplicate entry > '3-6045-2128322' for key 'PRIMARY'/ > > *Error*reported on 2015-10-10 06:05:55 forbuild #6045 > > /(Label::InsertAssociation): SQL error: Duplicate entry > '3-6045-2101680' for key 'PRIMARY'/ > > *Error*reported on 2015-10-10 06:05:55 forbuild #6045 > > /(Label::InsertAssociation): SQL error: Duplicate entry > '3-6045-2101683' for key 'PRIMARY'/ > > *Error*reported on 2015-10-10 06:05:53 forbuild #6045 > > /(Label::InsertAssociation): SQL error: Duplicate entry > '2-6045-2128292' for key 'PRIMARY'/ > > *Error*reported on 2015-10-10 06:05:53 forbuild #6045 > > /(Label::InsertAssociation): SQL error: Duplicate entry > '3-6045-2128302' for key 'PRIMARY'/ > > > On 10/7/2015 7:30 AM, Zack Galbreath wrote: >> Hi Burlen, >> >> On Wed, Oct 7, 2015 at 10:14 AM, Burlen Loring > > wrote: >> >> Anyone know what this cdash error is about? It recently began >> appearing and results for some submissions are not displayed on >> the main page. >> >> >> These errors aren't familiar to me. If you have the permissions >> necessary to edit config.local.php, try temporarily setting >> $CDASH_PRODUCTION_MODE to false. This will show you the actual >> queries that are failing, rather than "query hidden". > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 4208 bytes Desc: not available URL: From clinton at elemtech.com Thu Oct 15 21:00:27 2015 From: clinton at elemtech.com (clinton at elemtech.com) Date: Thu, 15 Oct 2015 19:00:27 -0600 Subject: [Cdash] SQL error: SQL error encountered, query hidden. In-Reply-To: <5620305A.7070908@lbl.gov> Message-ID: <4f968da0-9691-4de8-9589-6397d7148916@email.android.com> I had this problem before. Perhaps this thread will help. http://public.kitware.com/pipermail/cdash/2015-April/001601.html Clint On Oct 15, 2015 5:01 PM, Burlen Loring wrote: > > OK, so our disk was full. that may have caused some of this. we will see tonight if the error go away. > > One issue is that cdash had submission xml files starting from over a year ago until the disk got full in ./backup. > > in my config.loval.php I have : CDASH_BACKUP_TIMEFRAME=48 > > cdash is supposed to delete them after 48 hours right? any idea why it might not be deleted? > > > On 10/10/2015 02:32 PM, Burlen Loring wrote: > > thanks Zack, output below. Also when I go to the page to show the list of failed tests there are 4 entries for each test. > http://cdash.visit.lbl.gov/viewTest.php?onlyfailed&buildid=6045 > > Error Log > ?Error?reported on 2015-10-10 06:06:15 for?build #6045 > (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction > > ?Error?reported on 2015-10-10 06:06:14 for?build #6045 > (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction > > ?Error?reported on 2015-10-10 06:06:14 for?build #6045 > (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction > > ?Error?reported on 2015-10-10 06:06:14 for?build #6045 > (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction > > ?Error?reported on 2015-10-10 06:06:14 for?build #6045 > (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction > > ?Error?reported on 2015-10-10 06:05:57 for?build #6045 > (Label::InsertAssociation): SQL error: Duplicate entry '1-6045-2128329' for key 'PRIMARY' > > ?Error?reported on 2015-10-10 06:05:55 for?build #6045 > (Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2101676' for key 'PRIMARY' > > ?Error?reported on 2015-10-10 06:05:55 for?build #6045 > (Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2101678' for key 'PRIMARY' > > ?Error?reported on 2015-10-10 06:05:55 for?build #6045 > (Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2128322' for key 'PRIMARY' > > ?Error?reported on 2015-10-10 06:05:55 for?build #6045 > (Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2101680' for key 'PRIMARY' > > ?Error?reported on 2015-10-10 06:05:55 for?build #6045 > (Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2101683' for key 'PRIMARY' > > ?Error?reported on 2015-10-10 06:05:53 for?build #6045 > (Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2128292' for key 'PRIMARY' > > ?Error?reported on 2015-10-10 06:05:53 for?build #6045 > (Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2128302' for key 'PRIMARY' > > > On 10/7/2015 7:30 AM, Zack Galbreath wrote: >> >> Hi Burlen, >> >> On Wed, Oct 7, 2015 at 10:14 AM, Burlen Loring wrote: >>> >>> Anyone know what this cdash error is about? It recently began appearing and results for some submissions are not displayed on the main page. >> >> >> These errors aren't familiar to me.? If you have the permissions necessary to edit config.local.php, try temporarily setting $CDASH_PRODUCTION_MODE to false.? This will show you the actual queries that are failing, rather than "query hidden". > > > From bloring at lbl.gov Fri Oct 16 12:28:26 2015 From: bloring at lbl.gov (Burlen Loring) Date: Fri, 16 Oct 2015 09:28:26 -0700 Subject: [Cdash] SQL error: SQL error encountered, query hidden. In-Reply-To: <4f968da0-9691-4de8-9589-6397d7148916@email.android.com> References: <4f968da0-9691-4de8-9589-6397d7148916@email.android.com> Message-ID: <562125AA.50906@lbl.gov> Clint, thank you! That certainly sounds promising. we are using virtual hosts too. I updated our config based on your suggestion. We will see if that helps! from last night submissions I can see that we still have the same error as reported below. the disk issue is separate from the mysql lock issue. There's actually a lot of info about how to solve this lock issue on line. Maybe I can try some of the suggestions. Thanks! Burlen On 10/15/2015 06:00 PM, clinton at elemtech.com wrote: > I had this problem before. > > Perhaps this thread will help. > http://public.kitware.com/pipermail/cdash/2015-April/001601.html > > Clint > > On Oct 15, 2015 5:01 PM, Burlen Loring wrote: >> OK, so our disk was full. that may have caused some of this. we will see tonight if the error go away. >> >> One issue is that cdash had submission xml files starting from over a year ago until the disk got full in ./backup. >> >> in my config.loval.php I have : CDASH_BACKUP_TIMEFRAME=48 >> >> cdash is supposed to delete them after 48 hours right? any idea why it might not be deleted? >> >> >> On 10/10/2015 02:32 PM, Burlen Loring wrote: >> >> thanks Zack, output below. Also when I go to the page to show the list of failed tests there are 4 entries for each test. >> http://cdash.visit.lbl.gov/viewTest.php?onlyfailed&buildid=6045 >> >> Error Log >> Error reported on 2015-10-10 06:06:15 for build #6045 >> (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction >> >> Error reported on 2015-10-10 06:06:14 for build #6045 >> (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction >> >> Error reported on 2015-10-10 06:06:14 for build #6045 >> (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction >> >> Error reported on 2015-10-10 06:06:14 for build #6045 >> (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction >> >> Error reported on 2015-10-10 06:06:14 for build #6045 >> (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction >> >> Error reported on 2015-10-10 06:05:57 for build #6045 >> (Label::InsertAssociation): SQL error: Duplicate entry '1-6045-2128329' for key 'PRIMARY' >> >> Error reported on 2015-10-10 06:05:55 for build #6045 >> (Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2101676' for key 'PRIMARY' >> >> Error reported on 2015-10-10 06:05:55 for build #6045 >> (Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2101678' for key 'PRIMARY' >> >> Error reported on 2015-10-10 06:05:55 for build #6045 >> (Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2128322' for key 'PRIMARY' >> >> Error reported on 2015-10-10 06:05:55 for build #6045 >> (Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2101680' for key 'PRIMARY' >> >> Error reported on 2015-10-10 06:05:55 for build #6045 >> (Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2101683' for key 'PRIMARY' >> >> Error reported on 2015-10-10 06:05:53 for build #6045 >> (Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2128292' for key 'PRIMARY' >> >> Error reported on 2015-10-10 06:05:53 for build #6045 >> (Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2128302' for key 'PRIMARY' >> >> >> On 10/7/2015 7:30 AM, Zack Galbreath wrote: >>> Hi Burlen, >>> >>> On Wed, Oct 7, 2015 at 10:14 AM, Burlen Loring wrote: >>>> Anyone know what this cdash error is about? It recently began appearing and results for some submissions are not displayed on the main page. >>> >>> These errors aren't familiar to me. If you have the permissions necessary to edit config.local.php, try temporarily setting $CDASH_PRODUCTION_MODE to false. This will show you the actual queries that are failing, rather than "query hidden". >> >> From DLRdave at aol.com Thu Oct 22 09:04:20 2015 From: DLRdave at aol.com (David Cole) Date: Thu, 22 Oct 2015 09:04:20 -0400 Subject: [Cdash] Problem sorting by the Time column Message-ID: In the Google Chrome browser, this page does not sort properly by the Time column: https://open.cdash.org/viewTest.php?onlypassed&buildid=4065227 Same exact misbehavior in Firefox, too. On Windows 8.1. Known problem? Thanks, David C. From zack.galbreath at kitware.com Thu Oct 22 09:35:21 2015 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Thu, 22 Oct 2015 09:35:21 -0400 Subject: [Cdash] Problem sorting by the Time column In-Reply-To: References: Message-ID: Thanks for the report. As luck would have it, I'm currently working on viewTest.php. My hope is to improve its performance when thousands of tests are present (like ITK). I'll make sure to take another look at sorting too. On Thu, Oct 22, 2015 at 9:04 AM, David Cole via Cdash < cdash at public.kitware.com> wrote: > In the Google Chrome browser, this page does not sort properly by the > Time column: > https://open.cdash.org/viewTest.php?onlypassed&buildid=4065227 > > Same exact misbehavior in Firefox, too. On Windows 8.1. > > Known problem? > > > Thanks, > David C. > _______________________________________________ > Cdash mailing list > Cdash at public.kitware.com > http://public.kitware.com/mailman/listinfo/cdash > -------------- next part -------------- An HTML attachment was scrubbed... URL: From DLRdave at aol.com Fri Oct 23 14:04:42 2015 From: DLRdave at aol.com (David Cole) Date: Fri, 23 Oct 2015 14:04:42 -0400 Subject: [CDash] [Cdash] Problem sorting by the Time column In-Reply-To: References: Message-ID: On a not unrelated note... Since this set of updates: https://open.cdash.org/viewChanges.php?project=CDash&date=2015-10-07 80+ tests are failing persistently on multiple submitters every night on the CDash dashboard. Are any of the 3 authors involved (you, Patrick Reynolds and Jamie Snape) planning to fix these test failures? Even before that, there were a handful of persistently failing tests on several dashboard submitters. I know from painful experience that it is difficult to diagnose CDash test failures sometimes, but the current state of the system would appear to be quite miserable. Only 1 out of 85 tests passes on the machine I'm submitting a dashboard from..... ?? On Thu, Oct 22, 2015 at 9:35 AM, Zack Galbreath wrote: > Thanks for the report. > > As luck would have it, I'm currently working on viewTest.php. My hope is to > improve its performance when thousands of tests are present (like ITK). > I'll make sure to take another look at sorting too. > > > > On Thu, Oct 22, 2015 at 9:04 AM, David Cole via Cdash > wrote: >> >> In the Google Chrome browser, this page does not sort properly by the >> Time column: >> https://open.cdash.org/viewTest.php?onlypassed&buildid=4065227 >> >> Same exact misbehavior in Firefox, too. On Windows 8.1. >> >> Known problem? >> >> >> Thanks, >> David C. >> _______________________________________________ >> Cdash mailing list >> Cdash at public.kitware.com >> http://public.kitware.com/mailman/listinfo/cdash > > From zack.galbreath at kitware.com Fri Oct 23 15:06:15 2015 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Fri, 23 Oct 2015 15:06:15 -0400 Subject: [CDash] [Cdash] Problem sorting by the Time column In-Reply-To: References: Message-ID: On Fri, Oct 23, 2015 at 2:04 PM, David Cole wrote: > On a not unrelated note... > > Since this set of updates: > https://open.cdash.org/viewChanges.php?project=CDash&date=2015-10-07 > > 80+ tests are failing persistently on multiple submitters every night > on the CDash dashboard. > > Are any of the 3 authors involved (you, Patrick Reynolds and Jamie > Snape) planning to fix these test failures? > This update introduced a new installation step that the site maintainers will need to perform: https://github.com/Kitware/CDash#installation Even before that, there were a handful of persistently failing tests > on several dashboard submitters. > > I know from painful experience that it is difficult to diagnose CDash > test failures sometimes, but the current state of the system would > appear to be quite miserable. Only 1 out of 85 tests passes on the > machine I'm submitting a dashboard from..... > It's true that there's still a couple flaky tests floating around, but hopefully we'll be able to fix these up. The goal is to be get trustworthy pass/fail results from CircleCI whenever a pull request is created. -------------- next part -------------- An HTML attachment was scrubbed... URL: From DLRdave at aol.com Fri Oct 23 15:40:39 2015 From: DLRdave at aol.com (David Cole) Date: Fri, 23 Oct 2015 15:40:39 -0400 Subject: [CDash] [Cdash] Problem sorting by the Time column In-Reply-To: References: Message-ID: On Fri, Oct 23, 2015 at 3:06 PM, Zack Galbreath wrote: > ... > > This update introduced a new installation step that the site maintainers > will need to perform: > > https://github.com/Kitware/CDash#installation > Perhaps an email notification to this list might have been a good idea then? ;-) > > It's true that there's still a couple flaky tests floating around, but > hopefully we'll be able to fix these up. The goal is to be get trustworthy > pass/fail results from CircleCI whenever a pull request is created. Good to know. Thanks, D From nilsgladitz at gmail.com Sat Oct 24 11:03:44 2015 From: nilsgladitz at gmail.com (Nils Gladitz) Date: Sat, 24 Oct 2015 17:03:44 +0200 Subject: [CDash] [Cdash] Problem sorting by the Time column In-Reply-To: References: Message-ID: <562B9DD0.5030903@gmail.com> On 23.10.2015 21:40, David Cole via CDash wrote: > On Fri, Oct 23, 2015 at 3:06 PM, Zack Galbreath > wrote: >> ... >> >> This update introduced a new installation step that the site maintainers >> will need to perform: >> >> https://github.com/Kitware/CDash#installation >> > Perhaps an email notification to this list might have been a good idea then? ;-) > After following the discussion here I updated my site (nibble) accordingly. My MySQL submission now mostly works (3 remaining failures) but PostgreSQL seems to be still mostly broken (80 failures). Nils From zack.galbreath at kitware.com Mon Oct 26 14:38:54 2015 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Mon, 26 Oct 2015 14:38:54 -0400 Subject: [CDash] [Cdash] Problem sorting by the Time column In-Reply-To: <562B9DD0.5030903@gmail.com> References: <562B9DD0.5030903@gmail.com> Message-ID: On Sat, Oct 24, 2015 at 11:03 AM, Nils Gladitz wrote: > After following the discussion here I updated my site (nibble) accordingly. > > My MySQL submission now mostly works (3 remaining failures) but PostgreSQL > seems to be still mostly broken (80 failures). > Thanks for taking the time to update your site. I'm also running a PostgreSQL submission (nix.kitware) and I'm not encountering the same failing tests that you are. It looks like your site is failing during the install test, but further details are scarce. If you get a chance, could you see if there's any relevant details in any of the error logs (CDash/PHP/postgres)? -------------- next part -------------- An HTML attachment was scrubbed... URL: From nilsgladitz at gmail.com Mon Oct 26 15:34:39 2015 From: nilsgladitz at gmail.com (Nils Gladitz) Date: Mon, 26 Oct 2015 20:34:39 +0100 Subject: [CDash] [Cdash] Problem sorting by the Time column In-Reply-To: References: <562B9DD0.5030903@gmail.com> Message-ID: <562E804F.4030804@gmail.com> On 26.10.2015 19:38, Zack Galbreath wrote: > On Sat, Oct 24, 2015 at 11:03 AM, Nils Gladitz > wrote: > > After following the discussion here I updated my site (nibble) > accordingly. > > My MySQL submission now mostly works (3 remaining failures) but > PostgreSQL seems to be still mostly broken (80 failures). > > > Thanks for taking the time to update your site. > > I'm also running a PostgreSQL submission (nix.kitware) and I'm not > encountering the same failing tests that you are. It looks like your > site is failing during the install test, but further details are > scarce. If you get a chance, could you see if there's any relevant > details in any of the error logs (CDash/PHP/postgres)? Thanks for the pointer. The install test output for my last two submissions contains: Error connecting to host postgres database. Tried names 'host' and 'postgres' Error connecting to host postgres database. Tried names 'host' and 'postgres' I tried running the install test manually from the nightly build directory where it previously failed (ctest -R install -V) but this time it ran fine. Running all tests I even got to "15 tests failed out of 97". I also run a submission for "Release-2-2-2" with PostgreSQL from the same machine and it also does not show those issues. I have no idea what is going on there. Nils -------------- next part -------------- An HTML attachment was scrubbed... URL: From nilsgladitz at gmail.com Tue Oct 27 05:35:34 2015 From: nilsgladitz at gmail.com (Nils Gladitz) Date: Tue, 27 Oct 2015 10:35:34 +0100 Subject: [CDash] "install" test issues In-Reply-To: <562E804F.4030804@gmail.com> References: <562B9DD0.5030903@gmail.com> <562E804F.4030804@gmail.com> Message-ID: <562F4566.1000407@gmail.com> On 10/26/2015 08:34 PM, Nils Gladitz wrote: > On 26.10.2015 19:38, Zack Galbreath wrote: >> >> >> I'm also running a PostgreSQL submission (nix.kitware) and I'm not >> encountering the same failing tests that you are. It looks like your >> site is failing during the install test, but further details are >> scarce. If you get a chance, could you see if there's any relevant >> details in any of the error logs (CDash/PHP/postgres)? > > I have no idea what is going on there I set up a new instance on a different machine for testing. One issue I found seems to be https://github.com/Kitware/CDash/blob/master/install.php#L114 which in my case resulted in 'database "cdash" does not exist'. I think it tries the "cdash" database here because no database name was given and "cdash" happens to be the name of my database user; I assume it was working for you because in your case there was an existing database with the name of your user(?) pdo_select_db("$CDASH_DB_NAME") seems to help in my case but I don't know if that is the correct fix. On a somewhat related note the "install" test seems to falsely pass when using a user without database creation privileges: test 1 Start 1: install 1: Test command: /usr/bin/php "/var/www/html/CDash/tests/singletest.php" "/var/www/html/CDash/tests/test_install.php" 1: Test timeout computed to be: 1500 1: /var/www/html/CDash/tests/test_install.php 1: All Tests 1: Error connecting to host postgres database. 1: Tried names 'host' and 'postgres' 1: Error connecting to host postgres database. 1: Tried names 'host' and 'postgres' 1: Error File: /var/www/html/CDash/tests/test_install.php on line: 34: error query(CREATE DATABASE) 1/1 Test #1: install .......................... Passed 0.08 sec The following tests passed: install Nils -------------- next part -------------- An HTML attachment was scrubbed... URL: From bloring at lbl.gov Fri Oct 2 18:43:27 2015 From: bloring at lbl.gov (Burlen Loring) Date: Fri, 02 Oct 2015 11:43:27 -0700 Subject: [Cdash] cdash bug Message-ID: <560ED04F.1030709@lbl.gov> Hi All, Ever since we upgraded to cdash 2.2.2 the web display has been broken for tests that have multiple image diffs. We are now running 2.2.3 and still have the issue. The interactive image widget is only displayed for the first failure. It needs to be displayed for each failure. This can be reproduced using ctest with ParaView. Here is an experimental submission to ParaView dashboard illustrating the issue. There are 4 failures, but only one interactive widget displayed. https://open.cdash.org/testDetails.php?test=379396531&build=4043227 steps to reproduce in ParaView ctest: 1) find a test case that has multiple image diffs, I chose vtkSciberQuestCxx-MPI-TestVortexFilter because I know it has multiple tests 2) modify two or more of the baseline in an image editor to produce a failure 3) run the test and send it to the dashboard I filed a bug report, http://public.kitware.com/Bug/view.php?id=15764 This is a major obstacle in our transition to ctest, can you comment on plans to address it? Please let me know if there is a work around in the mean time. Thanks Burlen -------------- next part -------------- An HTML attachment was scrubbed... URL: From bloring at lbl.gov Wed Oct 7 14:14:17 2015 From: bloring at lbl.gov (Burlen Loring) Date: Wed, 7 Oct 2015 07:14:17 -0700 Subject: [Cdash] SQL error: SQL error encountered, query hidden. Message-ID: <561528B9.9010906@lbl.gov> Anyone know what this cdash error is about? It recently began appearing and results for some submissions are not displayed on the main page. *Error * reported on 2015-10-07 05:57:44 for build #6012 /(compute_test_difference): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:43 for build #6012 /(compute_test_difference): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:43 for build #6012 /(compute_test_difference): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:34 for build #6012 /(Label::InsertAssociation): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:31 for build #6012 /(Label::InsertAssociation): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:23 for build #6012 /(Label::InsertAssociation): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:23 for build #6012 /(Label::InsertAssociation): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:23 for build #6012 /(Label::InsertAssociation): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:23 for build #6012 /(Label::InsertAssociation): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:19 for build #6012 /(Label::InsertAssociation): SQL error: SQL error encountered, query hidden./ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: error.png Type: image/png Size: 4208 bytes Desc: not available URL: From zack.galbreath at kitware.com Wed Oct 7 14:30:10 2015 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Wed, 7 Oct 2015 10:30:10 -0400 Subject: [Cdash] SQL error: SQL error encountered, query hidden. In-Reply-To: <561528B9.9010906@lbl.gov> References: <561528B9.9010906@lbl.gov> Message-ID: Hi Burlen, On Wed, Oct 7, 2015 at 10:14 AM, Burlen Loring wrote: > Anyone know what this cdash error is about? It recently began appearing > and results for some submissions are not displayed on the main page. > These errors aren't familiar to me. If you have the permissions necessary to edit config.local.php, try temporarily setting $CDASH_PRODUCTION_MODE to false. This will show you the actual queries that are failing, rather than "query hidden". -------------- next part -------------- An HTML attachment was scrubbed... URL: From bloring at lbl.gov Sat Oct 10 21:32:16 2015 From: bloring at lbl.gov (Burlen Loring) Date: Sat, 10 Oct 2015 14:32:16 -0700 Subject: [Cdash] SQL error: SQL error encountered, query hidden. In-Reply-To: References: <561528B9.9010906@lbl.gov> Message-ID: <561983E0.6010207@lbl.gov> thanks Zack, output below. Also when I go to the page to show the list of failed tests there are 4 entries for each test. http://cdash.visit.lbl.gov/viewTest.php?onlyfailed&buildid=6045 Error Log *Error*reported on 2015-10-10 06:06:15 forbuild #6045 /(compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction/ *Error*reported on 2015-10-10 06:06:14 forbuild #6045 /(compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction/ *Error*reported on 2015-10-10 06:06:14 forbuild #6045 /(compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction/ *Error*reported on 2015-10-10 06:06:14 forbuild #6045 /(compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction/ *Error*reported on 2015-10-10 06:06:14 forbuild #6045 /(compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction/ *Error*reported on 2015-10-10 06:05:57 forbuild #6045 /(Label::InsertAssociation): SQL error: Duplicate entry '1-6045-2128329' for key 'PRIMARY'/ *Error*reported on 2015-10-10 06:05:55 forbuild #6045 /(Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2101676' for key 'PRIMARY'/ *Error*reported on 2015-10-10 06:05:55 forbuild #6045 /(Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2101678' for key 'PRIMARY'/ *Error*reported on 2015-10-10 06:05:55 forbuild #6045 /(Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2128322' for key 'PRIMARY'/ *Error*reported on 2015-10-10 06:05:55 forbuild #6045 /(Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2101680' for key 'PRIMARY'/ *Error*reported on 2015-10-10 06:05:55 forbuild #6045 /(Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2101683' for key 'PRIMARY'/ *Error*reported on 2015-10-10 06:05:53 forbuild #6045 /(Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2128292' for key 'PRIMARY'/ *Error*reported on 2015-10-10 06:05:53 forbuild #6045 /(Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2128302' for key 'PRIMARY'/ On 10/7/2015 7:30 AM, Zack Galbreath wrote: > Hi Burlen, > > On Wed, Oct 7, 2015 at 10:14 AM, Burlen Loring > wrote: > > Anyone know what this cdash error is about? It recently began > appearing and results for some submissions are not displayed on > the main page. > > > These errors aren't familiar to me. If you have the permissions > necessary to edit config.local.php, try temporarily setting > $CDASH_PRODUCTION_MODE to false. This will show you the actual > queries that are failing, rather than "query hidden". -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: error.png Type: image/png Size: 4208 bytes Desc: not available URL: From mike.jackson at bluequartz.net Thu Oct 15 13:40:27 2015 From: mike.jackson at bluequartz.net (Michael Jackson) Date: Thu, 15 Oct 2015 09:40:27 -0400 Subject: [Cdash] Server Down Message-ID: is my.cdash.org down? -- Mike Jackson From bill.hoffman at kitware.com Thu Oct 15 15:46:13 2015 From: bill.hoffman at kitware.com (Bill Hoffman) Date: Thu, 15 Oct 2015 11:46:13 -0400 Subject: [Cdash] Server Down In-Reply-To: References: Message-ID: <561FCA45.6080709@kitware.com> On 10/15/2015 9:40 AM, Michael Jackson wrote: > is my.cdash.org down? Yes, we are working on it. Thanks for the report. -- Bill Hoffman Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 bill.hoffman at kitware.com http://www.kitware.com 518 881-4905 (Direct) 518 371-3971 x105 Fax (518) 371-4573 From bloring at lbl.gov Thu Oct 15 23:01:46 2015 From: bloring at lbl.gov (Burlen Loring) Date: Thu, 15 Oct 2015 16:01:46 -0700 Subject: [Cdash] SQL error: SQL error encountered, query hidden. In-Reply-To: <561983E0.6010207@lbl.gov> References: <561528B9.9010906@lbl.gov> <561983E0.6010207@lbl.gov> Message-ID: <5620305A.7070908@lbl.gov> OK, so our disk was full. that may have caused some of this. we will see tonight if the error go away. One issue is that cdash had submission xml files starting from over a year ago until the disk got full in ./backup. in my config.loval.php I have : CDASH_BACKUP_TIMEFRAME=48 cdash is supposed to delete them after 48 hours right? any idea why it might not be deleted? On 10/10/2015 02:32 PM, Burlen Loring wrote: > thanks Zack, output below. Also when I go to the page to show the list > of failed tests there are 4 entries for each test. > http://cdash.visit.lbl.gov/viewTest.php?onlyfailed&buildid=6045 > > > Error Log > > *Error*reported on 2015-10-10 06:06:15 forbuild #6045 > > /(compute_test_difference): SQL error: Deadlock found when trying to > get lock; try restarting transaction/ > > *Error*reported on 2015-10-10 06:06:14 forbuild #6045 > > /(compute_test_difference): SQL error: Deadlock found when trying to > get lock; try restarting transaction/ > > *Error*reported on 2015-10-10 06:06:14 forbuild #6045 > > /(compute_test_difference): SQL error: Deadlock found when trying to > get lock; try restarting transaction/ > > *Error*reported on 2015-10-10 06:06:14 forbuild #6045 > > /(compute_test_difference): SQL error: Deadlock found when trying to > get lock; try restarting transaction/ > > *Error*reported on 2015-10-10 06:06:14 forbuild #6045 > > /(compute_test_difference): SQL error: Deadlock found when trying to > get lock; try restarting transaction/ > > *Error*reported on 2015-10-10 06:05:57 forbuild #6045 > > /(Label::InsertAssociation): SQL error: Duplicate entry > '1-6045-2128329' for key 'PRIMARY'/ > > *Error*reported on 2015-10-10 06:05:55 forbuild #6045 > > /(Label::InsertAssociation): SQL error: Duplicate entry > '2-6045-2101676' for key 'PRIMARY'/ > > *Error*reported on 2015-10-10 06:05:55 forbuild #6045 > > /(Label::InsertAssociation): SQL error: Duplicate entry > '2-6045-2101678' for key 'PRIMARY'/ > > *Error*reported on 2015-10-10 06:05:55 forbuild #6045 > > /(Label::InsertAssociation): SQL error: Duplicate entry > '3-6045-2128322' for key 'PRIMARY'/ > > *Error*reported on 2015-10-10 06:05:55 forbuild #6045 > > /(Label::InsertAssociation): SQL error: Duplicate entry > '3-6045-2101680' for key 'PRIMARY'/ > > *Error*reported on 2015-10-10 06:05:55 forbuild #6045 > > /(Label::InsertAssociation): SQL error: Duplicate entry > '3-6045-2101683' for key 'PRIMARY'/ > > *Error*reported on 2015-10-10 06:05:53 forbuild #6045 > > /(Label::InsertAssociation): SQL error: Duplicate entry > '2-6045-2128292' for key 'PRIMARY'/ > > *Error*reported on 2015-10-10 06:05:53 forbuild #6045 > > /(Label::InsertAssociation): SQL error: Duplicate entry > '3-6045-2128302' for key 'PRIMARY'/ > > > On 10/7/2015 7:30 AM, Zack Galbreath wrote: >> Hi Burlen, >> >> On Wed, Oct 7, 2015 at 10:14 AM, Burlen Loring > > wrote: >> >> Anyone know what this cdash error is about? It recently began >> appearing and results for some submissions are not displayed on >> the main page. >> >> >> These errors aren't familiar to me. If you have the permissions >> necessary to edit config.local.php, try temporarily setting >> $CDASH_PRODUCTION_MODE to false. This will show you the actual >> queries that are failing, rather than "query hidden". > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 4208 bytes Desc: not available URL: From clinton at elemtech.com Fri Oct 16 01:00:27 2015 From: clinton at elemtech.com (clinton at elemtech.com) Date: Thu, 15 Oct 2015 19:00:27 -0600 Subject: [Cdash] SQL error: SQL error encountered, query hidden. In-Reply-To: <5620305A.7070908@lbl.gov> Message-ID: <4f968da0-9691-4de8-9589-6397d7148916@email.android.com> I had this problem before. Perhaps this thread will help. http://public.kitware.com/pipermail/cdash/2015-April/001601.html Clint On Oct 15, 2015 5:01 PM, Burlen Loring wrote: > > OK, so our disk was full. that may have caused some of this. we will see tonight if the error go away. > > One issue is that cdash had submission xml files starting from over a year ago until the disk got full in ./backup. > > in my config.loval.php I have : CDASH_BACKUP_TIMEFRAME=48 > > cdash is supposed to delete them after 48 hours right? any idea why it might not be deleted? > > > On 10/10/2015 02:32 PM, Burlen Loring wrote: > > thanks Zack, output below. Also when I go to the page to show the list of failed tests there are 4 entries for each test. > http://cdash.visit.lbl.gov/viewTest.php?onlyfailed&buildid=6045 > > Error Log > ?Error?reported on 2015-10-10 06:06:15 for?build #6045 > (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction > > ?Error?reported on 2015-10-10 06:06:14 for?build #6045 > (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction > > ?Error?reported on 2015-10-10 06:06:14 for?build #6045 > (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction > > ?Error?reported on 2015-10-10 06:06:14 for?build #6045 > (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction > > ?Error?reported on 2015-10-10 06:06:14 for?build #6045 > (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction > > ?Error?reported on 2015-10-10 06:05:57 for?build #6045 > (Label::InsertAssociation): SQL error: Duplicate entry '1-6045-2128329' for key 'PRIMARY' > > ?Error?reported on 2015-10-10 06:05:55 for?build #6045 > (Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2101676' for key 'PRIMARY' > > ?Error?reported on 2015-10-10 06:05:55 for?build #6045 > (Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2101678' for key 'PRIMARY' > > ?Error?reported on 2015-10-10 06:05:55 for?build #6045 > (Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2128322' for key 'PRIMARY' > > ?Error?reported on 2015-10-10 06:05:55 for?build #6045 > (Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2101680' for key 'PRIMARY' > > ?Error?reported on 2015-10-10 06:05:55 for?build #6045 > (Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2101683' for key 'PRIMARY' > > ?Error?reported on 2015-10-10 06:05:53 for?build #6045 > (Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2128292' for key 'PRIMARY' > > ?Error?reported on 2015-10-10 06:05:53 for?build #6045 > (Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2128302' for key 'PRIMARY' > > > On 10/7/2015 7:30 AM, Zack Galbreath wrote: >> >> Hi Burlen, >> >> On Wed, Oct 7, 2015 at 10:14 AM, Burlen Loring wrote: >>> >>> Anyone know what this cdash error is about? It recently began appearing and results for some submissions are not displayed on the main page. >> >> >> These errors aren't familiar to me.? If you have the permissions necessary to edit config.local.php, try temporarily setting $CDASH_PRODUCTION_MODE to false.? This will show you the actual queries that are failing, rather than "query hidden". > > > From bloring at lbl.gov Fri Oct 16 16:28:26 2015 From: bloring at lbl.gov (Burlen Loring) Date: Fri, 16 Oct 2015 09:28:26 -0700 Subject: [Cdash] SQL error: SQL error encountered, query hidden. In-Reply-To: <4f968da0-9691-4de8-9589-6397d7148916@email.android.com> References: <4f968da0-9691-4de8-9589-6397d7148916@email.android.com> Message-ID: <562125AA.50906@lbl.gov> Clint, thank you! That certainly sounds promising. we are using virtual hosts too. I updated our config based on your suggestion. We will see if that helps! from last night submissions I can see that we still have the same error as reported below. the disk issue is separate from the mysql lock issue. There's actually a lot of info about how to solve this lock issue on line. Maybe I can try some of the suggestions. Thanks! Burlen On 10/15/2015 06:00 PM, clinton at elemtech.com wrote: > I had this problem before. > > Perhaps this thread will help. > http://public.kitware.com/pipermail/cdash/2015-April/001601.html > > Clint > > On Oct 15, 2015 5:01 PM, Burlen Loring wrote: >> OK, so our disk was full. that may have caused some of this. we will see tonight if the error go away. >> >> One issue is that cdash had submission xml files starting from over a year ago until the disk got full in ./backup. >> >> in my config.loval.php I have : CDASH_BACKUP_TIMEFRAME=48 >> >> cdash is supposed to delete them after 48 hours right? any idea why it might not be deleted? >> >> >> On 10/10/2015 02:32 PM, Burlen Loring wrote: >> >> thanks Zack, output below. Also when I go to the page to show the list of failed tests there are 4 entries for each test. >> http://cdash.visit.lbl.gov/viewTest.php?onlyfailed&buildid=6045 >> >> Error Log >> Error reported on 2015-10-10 06:06:15 for build #6045 >> (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction >> >> Error reported on 2015-10-10 06:06:14 for build #6045 >> (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction >> >> Error reported on 2015-10-10 06:06:14 for build #6045 >> (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction >> >> Error reported on 2015-10-10 06:06:14 for build #6045 >> (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction >> >> Error reported on 2015-10-10 06:06:14 for build #6045 >> (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction >> >> Error reported on 2015-10-10 06:05:57 for build #6045 >> (Label::InsertAssociation): SQL error: Duplicate entry '1-6045-2128329' for key 'PRIMARY' >> >> Error reported on 2015-10-10 06:05:55 for build #6045 >> (Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2101676' for key 'PRIMARY' >> >> Error reported on 2015-10-10 06:05:55 for build #6045 >> (Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2101678' for key 'PRIMARY' >> >> Error reported on 2015-10-10 06:05:55 for build #6045 >> (Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2128322' for key 'PRIMARY' >> >> Error reported on 2015-10-10 06:05:55 for build #6045 >> (Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2101680' for key 'PRIMARY' >> >> Error reported on 2015-10-10 06:05:55 for build #6045 >> (Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2101683' for key 'PRIMARY' >> >> Error reported on 2015-10-10 06:05:53 for build #6045 >> (Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2128292' for key 'PRIMARY' >> >> Error reported on 2015-10-10 06:05:53 for build #6045 >> (Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2128302' for key 'PRIMARY' >> >> >> On 10/7/2015 7:30 AM, Zack Galbreath wrote: >>> Hi Burlen, >>> >>> On Wed, Oct 7, 2015 at 10:14 AM, Burlen Loring wrote: >>>> Anyone know what this cdash error is about? It recently began appearing and results for some submissions are not displayed on the main page. >>> >>> These errors aren't familiar to me. If you have the permissions necessary to edit config.local.php, try temporarily setting $CDASH_PRODUCTION_MODE to false. This will show you the actual queries that are failing, rather than "query hidden". >> >> From DLRdave at aol.com Thu Oct 22 13:04:20 2015 From: DLRdave at aol.com (David Cole) Date: Thu, 22 Oct 2015 09:04:20 -0400 Subject: [Cdash] Problem sorting by the Time column Message-ID: In the Google Chrome browser, this page does not sort properly by the Time column: https://open.cdash.org/viewTest.php?onlypassed&buildid=4065227 Same exact misbehavior in Firefox, too. On Windows 8.1. Known problem? Thanks, David C. From zack.galbreath at kitware.com Thu Oct 22 13:35:21 2015 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Thu, 22 Oct 2015 09:35:21 -0400 Subject: [Cdash] Problem sorting by the Time column In-Reply-To: References: Message-ID: Thanks for the report. As luck would have it, I'm currently working on viewTest.php. My hope is to improve its performance when thousands of tests are present (like ITK). I'll make sure to take another look at sorting too. On Thu, Oct 22, 2015 at 9:04 AM, David Cole via Cdash < cdash at public.kitware.com> wrote: > In the Google Chrome browser, this page does not sort properly by the > Time column: > https://open.cdash.org/viewTest.php?onlypassed&buildid=4065227 > > Same exact misbehavior in Firefox, too. On Windows 8.1. > > Known problem? > > > Thanks, > David C. > _______________________________________________ > Cdash mailing list > Cdash at public.kitware.com > http://public.kitware.com/mailman/listinfo/cdash > -------------- next part -------------- An HTML attachment was scrubbed... URL: From DLRdave at aol.com Fri Oct 23 18:04:42 2015 From: DLRdave at aol.com (David Cole) Date: Fri, 23 Oct 2015 14:04:42 -0400 Subject: [CDash] [Cdash] Problem sorting by the Time column In-Reply-To: References: Message-ID: On a not unrelated note... Since this set of updates: https://open.cdash.org/viewChanges.php?project=CDash&date=2015-10-07 80+ tests are failing persistently on multiple submitters every night on the CDash dashboard. Are any of the 3 authors involved (you, Patrick Reynolds and Jamie Snape) planning to fix these test failures? Even before that, there were a handful of persistently failing tests on several dashboard submitters. I know from painful experience that it is difficult to diagnose CDash test failures sometimes, but the current state of the system would appear to be quite miserable. Only 1 out of 85 tests passes on the machine I'm submitting a dashboard from..... ?? On Thu, Oct 22, 2015 at 9:35 AM, Zack Galbreath wrote: > Thanks for the report. > > As luck would have it, I'm currently working on viewTest.php. My hope is to > improve its performance when thousands of tests are present (like ITK). > I'll make sure to take another look at sorting too. > > > > On Thu, Oct 22, 2015 at 9:04 AM, David Cole via Cdash > wrote: >> >> In the Google Chrome browser, this page does not sort properly by the >> Time column: >> https://open.cdash.org/viewTest.php?onlypassed&buildid=4065227 >> >> Same exact misbehavior in Firefox, too. On Windows 8.1. >> >> Known problem? >> >> >> Thanks, >> David C. >> _______________________________________________ >> Cdash mailing list >> Cdash at public.kitware.com >> http://public.kitware.com/mailman/listinfo/cdash > > From zack.galbreath at kitware.com Fri Oct 23 19:06:15 2015 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Fri, 23 Oct 2015 15:06:15 -0400 Subject: [CDash] [Cdash] Problem sorting by the Time column In-Reply-To: References: Message-ID: On Fri, Oct 23, 2015 at 2:04 PM, David Cole wrote: > On a not unrelated note... > > Since this set of updates: > https://open.cdash.org/viewChanges.php?project=CDash&date=2015-10-07 > > 80+ tests are failing persistently on multiple submitters every night > on the CDash dashboard. > > Are any of the 3 authors involved (you, Patrick Reynolds and Jamie > Snape) planning to fix these test failures? > This update introduced a new installation step that the site maintainers will need to perform: https://github.com/Kitware/CDash#installation Even before that, there were a handful of persistently failing tests > on several dashboard submitters. > > I know from painful experience that it is difficult to diagnose CDash > test failures sometimes, but the current state of the system would > appear to be quite miserable. Only 1 out of 85 tests passes on the > machine I'm submitting a dashboard from..... > It's true that there's still a couple flaky tests floating around, but hopefully we'll be able to fix these up. The goal is to be get trustworthy pass/fail results from CircleCI whenever a pull request is created. -------------- next part -------------- An HTML attachment was scrubbed... URL: From DLRdave at aol.com Fri Oct 23 19:40:39 2015 From: DLRdave at aol.com (David Cole) Date: Fri, 23 Oct 2015 15:40:39 -0400 Subject: [CDash] [Cdash] Problem sorting by the Time column In-Reply-To: References: Message-ID: On Fri, Oct 23, 2015 at 3:06 PM, Zack Galbreath wrote: > ... > > This update introduced a new installation step that the site maintainers > will need to perform: > > https://github.com/Kitware/CDash#installation > Perhaps an email notification to this list might have been a good idea then? ;-) > > It's true that there's still a couple flaky tests floating around, but > hopefully we'll be able to fix these up. The goal is to be get trustworthy > pass/fail results from CircleCI whenever a pull request is created. Good to know. Thanks, D From nilsgladitz at gmail.com Sat Oct 24 15:03:44 2015 From: nilsgladitz at gmail.com (Nils Gladitz) Date: Sat, 24 Oct 2015 17:03:44 +0200 Subject: [CDash] [Cdash] Problem sorting by the Time column In-Reply-To: References: Message-ID: <562B9DD0.5030903@gmail.com> On 23.10.2015 21:40, David Cole via CDash wrote: > On Fri, Oct 23, 2015 at 3:06 PM, Zack Galbreath > wrote: >> ... >> >> This update introduced a new installation step that the site maintainers >> will need to perform: >> >> https://github.com/Kitware/CDash#installation >> > Perhaps an email notification to this list might have been a good idea then? ;-) > After following the discussion here I updated my site (nibble) accordingly. My MySQL submission now mostly works (3 remaining failures) but PostgreSQL seems to be still mostly broken (80 failures). Nils From zack.galbreath at kitware.com Mon Oct 26 18:38:54 2015 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Mon, 26 Oct 2015 14:38:54 -0400 Subject: [CDash] [Cdash] Problem sorting by the Time column In-Reply-To: <562B9DD0.5030903@gmail.com> References: <562B9DD0.5030903@gmail.com> Message-ID: On Sat, Oct 24, 2015 at 11:03 AM, Nils Gladitz wrote: > After following the discussion here I updated my site (nibble) accordingly. > > My MySQL submission now mostly works (3 remaining failures) but PostgreSQL > seems to be still mostly broken (80 failures). > Thanks for taking the time to update your site. I'm also running a PostgreSQL submission (nix.kitware) and I'm not encountering the same failing tests that you are. It looks like your site is failing during the install test, but further details are scarce. If you get a chance, could you see if there's any relevant details in any of the error logs (CDash/PHP/postgres)? -------------- next part -------------- An HTML attachment was scrubbed... URL: From nilsgladitz at gmail.com Mon Oct 26 19:34:39 2015 From: nilsgladitz at gmail.com (Nils Gladitz) Date: Mon, 26 Oct 2015 20:34:39 +0100 Subject: [CDash] [Cdash] Problem sorting by the Time column In-Reply-To: References: <562B9DD0.5030903@gmail.com> Message-ID: <562E804F.4030804@gmail.com> On 26.10.2015 19:38, Zack Galbreath wrote: > On Sat, Oct 24, 2015 at 11:03 AM, Nils Gladitz > wrote: > > After following the discussion here I updated my site (nibble) > accordingly. > > My MySQL submission now mostly works (3 remaining failures) but > PostgreSQL seems to be still mostly broken (80 failures). > > > Thanks for taking the time to update your site. > > I'm also running a PostgreSQL submission (nix.kitware) and I'm not > encountering the same failing tests that you are. It looks like your > site is failing during the install test, but further details are > scarce. If you get a chance, could you see if there's any relevant > details in any of the error logs (CDash/PHP/postgres)? Thanks for the pointer. The install test output for my last two submissions contains: Error connecting to host postgres database. Tried names 'host' and 'postgres' Error connecting to host postgres database. Tried names 'host' and 'postgres' I tried running the install test manually from the nightly build directory where it previously failed (ctest -R install -V) but this time it ran fine. Running all tests I even got to "15 tests failed out of 97". I also run a submission for "Release-2-2-2" with PostgreSQL from the same machine and it also does not show those issues. I have no idea what is going on there. Nils -------------- next part -------------- An HTML attachment was scrubbed... URL: From nilsgladitz at gmail.com Tue Oct 27 09:35:34 2015 From: nilsgladitz at gmail.com (Nils Gladitz) Date: Tue, 27 Oct 2015 10:35:34 +0100 Subject: [CDash] "install" test issues In-Reply-To: <562E804F.4030804@gmail.com> References: <562B9DD0.5030903@gmail.com> <562E804F.4030804@gmail.com> Message-ID: <562F4566.1000407@gmail.com> On 10/26/2015 08:34 PM, Nils Gladitz wrote: > On 26.10.2015 19:38, Zack Galbreath wrote: >> >> >> I'm also running a PostgreSQL submission (nix.kitware) and I'm not >> encountering the same failing tests that you are. It looks like your >> site is failing during the install test, but further details are >> scarce. If you get a chance, could you see if there's any relevant >> details in any of the error logs (CDash/PHP/postgres)? > > I have no idea what is going on there I set up a new instance on a different machine for testing. One issue I found seems to be https://github.com/Kitware/CDash/blob/master/install.php#L114 which in my case resulted in 'database "cdash" does not exist'. I think it tries the "cdash" database here because no database name was given and "cdash" happens to be the name of my database user; I assume it was working for you because in your case there was an existing database with the name of your user(?) pdo_select_db("$CDASH_DB_NAME") seems to help in my case but I don't know if that is the correct fix. On a somewhat related note the "install" test seems to falsely pass when using a user without database creation privileges: test 1 Start 1: install 1: Test command: /usr/bin/php "/var/www/html/CDash/tests/singletest.php" "/var/www/html/CDash/tests/test_install.php" 1: Test timeout computed to be: 1500 1: /var/www/html/CDash/tests/test_install.php 1: All Tests 1: Error connecting to host postgres database. 1: Tried names 'host' and 'postgres' 1: Error connecting to host postgres database. 1: Tried names 'host' and 'postgres' 1: Error File: /var/www/html/CDash/tests/test_install.php on line: 34: error query(CREATE DATABASE) 1/1 Test #1: install .......................... Passed 0.08 sec The following tests passed: install Nils -------------- next part -------------- An HTML attachment was scrubbed... URL: From bloring at lbl.gov Fri Oct 2 18:43:27 2015 From: bloring at lbl.gov (Burlen Loring) Date: Fri, 02 Oct 2015 11:43:27 -0700 Subject: [Cdash] cdash bug Message-ID: <560ED04F.1030709@lbl.gov> Hi All, Ever since we upgraded to cdash 2.2.2 the web display has been broken for tests that have multiple image diffs. We are now running 2.2.3 and still have the issue. The interactive image widget is only displayed for the first failure. It needs to be displayed for each failure. This can be reproduced using ctest with ParaView. Here is an experimental submission to ParaView dashboard illustrating the issue. There are 4 failures, but only one interactive widget displayed. https://open.cdash.org/testDetails.php?test=379396531&build=4043227 steps to reproduce in ParaView ctest: 1) find a test case that has multiple image diffs, I chose vtkSciberQuestCxx-MPI-TestVortexFilter because I know it has multiple tests 2) modify two or more of the baseline in an image editor to produce a failure 3) run the test and send it to the dashboard I filed a bug report, http://public.kitware.com/Bug/view.php?id=15764 This is a major obstacle in our transition to ctest, can you comment on plans to address it? Please let me know if there is a work around in the mean time. Thanks Burlen -------------- next part -------------- An HTML attachment was scrubbed... URL: From bloring at lbl.gov Wed Oct 7 14:14:17 2015 From: bloring at lbl.gov (Burlen Loring) Date: Wed, 7 Oct 2015 07:14:17 -0700 Subject: [Cdash] SQL error: SQL error encountered, query hidden. Message-ID: <561528B9.9010906@lbl.gov> Anyone know what this cdash error is about? It recently began appearing and results for some submissions are not displayed on the main page. *Error * reported on 2015-10-07 05:57:44 for build #6012 /(compute_test_difference): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:43 for build #6012 /(compute_test_difference): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:43 for build #6012 /(compute_test_difference): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:34 for build #6012 /(Label::InsertAssociation): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:31 for build #6012 /(Label::InsertAssociation): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:23 for build #6012 /(Label::InsertAssociation): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:23 for build #6012 /(Label::InsertAssociation): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:23 for build #6012 /(Label::InsertAssociation): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:23 for build #6012 /(Label::InsertAssociation): SQL error: SQL error encountered, query hidden./ *Error * reported on 2015-10-07 05:57:19 for build #6012 /(Label::InsertAssociation): SQL error: SQL error encountered, query hidden./ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: error.png Type: image/png Size: 4208 bytes Desc: not available URL: From zack.galbreath at kitware.com Wed Oct 7 14:30:10 2015 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Wed, 7 Oct 2015 10:30:10 -0400 Subject: [Cdash] SQL error: SQL error encountered, query hidden. In-Reply-To: <561528B9.9010906@lbl.gov> References: <561528B9.9010906@lbl.gov> Message-ID: Hi Burlen, On Wed, Oct 7, 2015 at 10:14 AM, Burlen Loring wrote: > Anyone know what this cdash error is about? It recently began appearing > and results for some submissions are not displayed on the main page. > These errors aren't familiar to me. If you have the permissions necessary to edit config.local.php, try temporarily setting $CDASH_PRODUCTION_MODE to false. This will show you the actual queries that are failing, rather than "query hidden". -------------- next part -------------- An HTML attachment was scrubbed... URL: From bloring at lbl.gov Sat Oct 10 21:32:16 2015 From: bloring at lbl.gov (Burlen Loring) Date: Sat, 10 Oct 2015 14:32:16 -0700 Subject: [Cdash] SQL error: SQL error encountered, query hidden. In-Reply-To: References: <561528B9.9010906@lbl.gov> Message-ID: <561983E0.6010207@lbl.gov> thanks Zack, output below. Also when I go to the page to show the list of failed tests there are 4 entries for each test. http://cdash.visit.lbl.gov/viewTest.php?onlyfailed&buildid=6045 Error Log *Error*reported on 2015-10-10 06:06:15 forbuild #6045 /(compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction/ *Error*reported on 2015-10-10 06:06:14 forbuild #6045 /(compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction/ *Error*reported on 2015-10-10 06:06:14 forbuild #6045 /(compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction/ *Error*reported on 2015-10-10 06:06:14 forbuild #6045 /(compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction/ *Error*reported on 2015-10-10 06:06:14 forbuild #6045 /(compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction/ *Error*reported on 2015-10-10 06:05:57 forbuild #6045 /(Label::InsertAssociation): SQL error: Duplicate entry '1-6045-2128329' for key 'PRIMARY'/ *Error*reported on 2015-10-10 06:05:55 forbuild #6045 /(Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2101676' for key 'PRIMARY'/ *Error*reported on 2015-10-10 06:05:55 forbuild #6045 /(Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2101678' for key 'PRIMARY'/ *Error*reported on 2015-10-10 06:05:55 forbuild #6045 /(Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2128322' for key 'PRIMARY'/ *Error*reported on 2015-10-10 06:05:55 forbuild #6045 /(Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2101680' for key 'PRIMARY'/ *Error*reported on 2015-10-10 06:05:55 forbuild #6045 /(Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2101683' for key 'PRIMARY'/ *Error*reported on 2015-10-10 06:05:53 forbuild #6045 /(Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2128292' for key 'PRIMARY'/ *Error*reported on 2015-10-10 06:05:53 forbuild #6045 /(Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2128302' for key 'PRIMARY'/ On 10/7/2015 7:30 AM, Zack Galbreath wrote: > Hi Burlen, > > On Wed, Oct 7, 2015 at 10:14 AM, Burlen Loring > wrote: > > Anyone know what this cdash error is about? It recently began > appearing and results for some submissions are not displayed on > the main page. > > > These errors aren't familiar to me. If you have the permissions > necessary to edit config.local.php, try temporarily setting > $CDASH_PRODUCTION_MODE to false. This will show you the actual > queries that are failing, rather than "query hidden". -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: error.png Type: image/png Size: 4208 bytes Desc: not available URL: From mike.jackson at bluequartz.net Thu Oct 15 13:40:27 2015 From: mike.jackson at bluequartz.net (Michael Jackson) Date: Thu, 15 Oct 2015 09:40:27 -0400 Subject: [Cdash] Server Down Message-ID: is my.cdash.org down? -- Mike Jackson From bill.hoffman at kitware.com Thu Oct 15 15:46:13 2015 From: bill.hoffman at kitware.com (Bill Hoffman) Date: Thu, 15 Oct 2015 11:46:13 -0400 Subject: [Cdash] Server Down In-Reply-To: References: Message-ID: <561FCA45.6080709@kitware.com> On 10/15/2015 9:40 AM, Michael Jackson wrote: > is my.cdash.org down? Yes, we are working on it. Thanks for the report. -- Bill Hoffman Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 bill.hoffman at kitware.com http://www.kitware.com 518 881-4905 (Direct) 518 371-3971 x105 Fax (518) 371-4573 From bloring at lbl.gov Thu Oct 15 23:01:46 2015 From: bloring at lbl.gov (Burlen Loring) Date: Thu, 15 Oct 2015 16:01:46 -0700 Subject: [Cdash] SQL error: SQL error encountered, query hidden. In-Reply-To: <561983E0.6010207@lbl.gov> References: <561528B9.9010906@lbl.gov> <561983E0.6010207@lbl.gov> Message-ID: <5620305A.7070908@lbl.gov> OK, so our disk was full. that may have caused some of this. we will see tonight if the error go away. One issue is that cdash had submission xml files starting from over a year ago until the disk got full in ./backup. in my config.loval.php I have : CDASH_BACKUP_TIMEFRAME=48 cdash is supposed to delete them after 48 hours right? any idea why it might not be deleted? On 10/10/2015 02:32 PM, Burlen Loring wrote: > thanks Zack, output below. Also when I go to the page to show the list > of failed tests there are 4 entries for each test. > http://cdash.visit.lbl.gov/viewTest.php?onlyfailed&buildid=6045 > > > Error Log > > *Error*reported on 2015-10-10 06:06:15 forbuild #6045 > > /(compute_test_difference): SQL error: Deadlock found when trying to > get lock; try restarting transaction/ > > *Error*reported on 2015-10-10 06:06:14 forbuild #6045 > > /(compute_test_difference): SQL error: Deadlock found when trying to > get lock; try restarting transaction/ > > *Error*reported on 2015-10-10 06:06:14 forbuild #6045 > > /(compute_test_difference): SQL error: Deadlock found when trying to > get lock; try restarting transaction/ > > *Error*reported on 2015-10-10 06:06:14 forbuild #6045 > > /(compute_test_difference): SQL error: Deadlock found when trying to > get lock; try restarting transaction/ > > *Error*reported on 2015-10-10 06:06:14 forbuild #6045 > > /(compute_test_difference): SQL error: Deadlock found when trying to > get lock; try restarting transaction/ > > *Error*reported on 2015-10-10 06:05:57 forbuild #6045 > > /(Label::InsertAssociation): SQL error: Duplicate entry > '1-6045-2128329' for key 'PRIMARY'/ > > *Error*reported on 2015-10-10 06:05:55 forbuild #6045 > > /(Label::InsertAssociation): SQL error: Duplicate entry > '2-6045-2101676' for key 'PRIMARY'/ > > *Error*reported on 2015-10-10 06:05:55 forbuild #6045 > > /(Label::InsertAssociation): SQL error: Duplicate entry > '2-6045-2101678' for key 'PRIMARY'/ > > *Error*reported on 2015-10-10 06:05:55 forbuild #6045 > > /(Label::InsertAssociation): SQL error: Duplicate entry > '3-6045-2128322' for key 'PRIMARY'/ > > *Error*reported on 2015-10-10 06:05:55 forbuild #6045 > > /(Label::InsertAssociation): SQL error: Duplicate entry > '3-6045-2101680' for key 'PRIMARY'/ > > *Error*reported on 2015-10-10 06:05:55 forbuild #6045 > > /(Label::InsertAssociation): SQL error: Duplicate entry > '3-6045-2101683' for key 'PRIMARY'/ > > *Error*reported on 2015-10-10 06:05:53 forbuild #6045 > > /(Label::InsertAssociation): SQL error: Duplicate entry > '2-6045-2128292' for key 'PRIMARY'/ > > *Error*reported on 2015-10-10 06:05:53 forbuild #6045 > > /(Label::InsertAssociation): SQL error: Duplicate entry > '3-6045-2128302' for key 'PRIMARY'/ > > > On 10/7/2015 7:30 AM, Zack Galbreath wrote: >> Hi Burlen, >> >> On Wed, Oct 7, 2015 at 10:14 AM, Burlen Loring > > wrote: >> >> Anyone know what this cdash error is about? It recently began >> appearing and results for some submissions are not displayed on >> the main page. >> >> >> These errors aren't familiar to me. If you have the permissions >> necessary to edit config.local.php, try temporarily setting >> $CDASH_PRODUCTION_MODE to false. This will show you the actual >> queries that are failing, rather than "query hidden". > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 4208 bytes Desc: not available URL: From clinton at elemtech.com Fri Oct 16 01:00:27 2015 From: clinton at elemtech.com (clinton at elemtech.com) Date: Thu, 15 Oct 2015 19:00:27 -0600 Subject: [Cdash] SQL error: SQL error encountered, query hidden. In-Reply-To: <5620305A.7070908@lbl.gov> Message-ID: <4f968da0-9691-4de8-9589-6397d7148916@email.android.com> I had this problem before. Perhaps this thread will help. http://public.kitware.com/pipermail/cdash/2015-April/001601.html Clint On Oct 15, 2015 5:01 PM, Burlen Loring wrote: > > OK, so our disk was full. that may have caused some of this. we will see tonight if the error go away. > > One issue is that cdash had submission xml files starting from over a year ago until the disk got full in ./backup. > > in my config.loval.php I have : CDASH_BACKUP_TIMEFRAME=48 > > cdash is supposed to delete them after 48 hours right? any idea why it might not be deleted? > > > On 10/10/2015 02:32 PM, Burlen Loring wrote: > > thanks Zack, output below. Also when I go to the page to show the list of failed tests there are 4 entries for each test. > http://cdash.visit.lbl.gov/viewTest.php?onlyfailed&buildid=6045 > > Error Log > ?Error?reported on 2015-10-10 06:06:15 for?build #6045 > (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction > > ?Error?reported on 2015-10-10 06:06:14 for?build #6045 > (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction > > ?Error?reported on 2015-10-10 06:06:14 for?build #6045 > (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction > > ?Error?reported on 2015-10-10 06:06:14 for?build #6045 > (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction > > ?Error?reported on 2015-10-10 06:06:14 for?build #6045 > (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction > > ?Error?reported on 2015-10-10 06:05:57 for?build #6045 > (Label::InsertAssociation): SQL error: Duplicate entry '1-6045-2128329' for key 'PRIMARY' > > ?Error?reported on 2015-10-10 06:05:55 for?build #6045 > (Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2101676' for key 'PRIMARY' > > ?Error?reported on 2015-10-10 06:05:55 for?build #6045 > (Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2101678' for key 'PRIMARY' > > ?Error?reported on 2015-10-10 06:05:55 for?build #6045 > (Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2128322' for key 'PRIMARY' > > ?Error?reported on 2015-10-10 06:05:55 for?build #6045 > (Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2101680' for key 'PRIMARY' > > ?Error?reported on 2015-10-10 06:05:55 for?build #6045 > (Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2101683' for key 'PRIMARY' > > ?Error?reported on 2015-10-10 06:05:53 for?build #6045 > (Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2128292' for key 'PRIMARY' > > ?Error?reported on 2015-10-10 06:05:53 for?build #6045 > (Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2128302' for key 'PRIMARY' > > > On 10/7/2015 7:30 AM, Zack Galbreath wrote: >> >> Hi Burlen, >> >> On Wed, Oct 7, 2015 at 10:14 AM, Burlen Loring wrote: >>> >>> Anyone know what this cdash error is about? It recently began appearing and results for some submissions are not displayed on the main page. >> >> >> These errors aren't familiar to me.? If you have the permissions necessary to edit config.local.php, try temporarily setting $CDASH_PRODUCTION_MODE to false.? This will show you the actual queries that are failing, rather than "query hidden". > > > From bloring at lbl.gov Fri Oct 16 16:28:26 2015 From: bloring at lbl.gov (Burlen Loring) Date: Fri, 16 Oct 2015 09:28:26 -0700 Subject: [Cdash] SQL error: SQL error encountered, query hidden. In-Reply-To: <4f968da0-9691-4de8-9589-6397d7148916@email.android.com> References: <4f968da0-9691-4de8-9589-6397d7148916@email.android.com> Message-ID: <562125AA.50906@lbl.gov> Clint, thank you! That certainly sounds promising. we are using virtual hosts too. I updated our config based on your suggestion. We will see if that helps! from last night submissions I can see that we still have the same error as reported below. the disk issue is separate from the mysql lock issue. There's actually a lot of info about how to solve this lock issue on line. Maybe I can try some of the suggestions. Thanks! Burlen On 10/15/2015 06:00 PM, clinton at elemtech.com wrote: > I had this problem before. > > Perhaps this thread will help. > http://public.kitware.com/pipermail/cdash/2015-April/001601.html > > Clint > > On Oct 15, 2015 5:01 PM, Burlen Loring wrote: >> OK, so our disk was full. that may have caused some of this. we will see tonight if the error go away. >> >> One issue is that cdash had submission xml files starting from over a year ago until the disk got full in ./backup. >> >> in my config.loval.php I have : CDASH_BACKUP_TIMEFRAME=48 >> >> cdash is supposed to delete them after 48 hours right? any idea why it might not be deleted? >> >> >> On 10/10/2015 02:32 PM, Burlen Loring wrote: >> >> thanks Zack, output below. Also when I go to the page to show the list of failed tests there are 4 entries for each test. >> http://cdash.visit.lbl.gov/viewTest.php?onlyfailed&buildid=6045 >> >> Error Log >> Error reported on 2015-10-10 06:06:15 for build #6045 >> (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction >> >> Error reported on 2015-10-10 06:06:14 for build #6045 >> (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction >> >> Error reported on 2015-10-10 06:06:14 for build #6045 >> (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction >> >> Error reported on 2015-10-10 06:06:14 for build #6045 >> (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction >> >> Error reported on 2015-10-10 06:06:14 for build #6045 >> (compute_test_difference): SQL error: Deadlock found when trying to get lock; try restarting transaction >> >> Error reported on 2015-10-10 06:05:57 for build #6045 >> (Label::InsertAssociation): SQL error: Duplicate entry '1-6045-2128329' for key 'PRIMARY' >> >> Error reported on 2015-10-10 06:05:55 for build #6045 >> (Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2101676' for key 'PRIMARY' >> >> Error reported on 2015-10-10 06:05:55 for build #6045 >> (Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2101678' for key 'PRIMARY' >> >> Error reported on 2015-10-10 06:05:55 for build #6045 >> (Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2128322' for key 'PRIMARY' >> >> Error reported on 2015-10-10 06:05:55 for build #6045 >> (Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2101680' for key 'PRIMARY' >> >> Error reported on 2015-10-10 06:05:55 for build #6045 >> (Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2101683' for key 'PRIMARY' >> >> Error reported on 2015-10-10 06:05:53 for build #6045 >> (Label::InsertAssociation): SQL error: Duplicate entry '2-6045-2128292' for key 'PRIMARY' >> >> Error reported on 2015-10-10 06:05:53 for build #6045 >> (Label::InsertAssociation): SQL error: Duplicate entry '3-6045-2128302' for key 'PRIMARY' >> >> >> On 10/7/2015 7:30 AM, Zack Galbreath wrote: >>> Hi Burlen, >>> >>> On Wed, Oct 7, 2015 at 10:14 AM, Burlen Loring wrote: >>>> Anyone know what this cdash error is about? It recently began appearing and results for some submissions are not displayed on the main page. >>> >>> These errors aren't familiar to me. If you have the permissions necessary to edit config.local.php, try temporarily setting $CDASH_PRODUCTION_MODE to false. This will show you the actual queries that are failing, rather than "query hidden". >> >> From DLRdave at aol.com Thu Oct 22 13:04:20 2015 From: DLRdave at aol.com (David Cole) Date: Thu, 22 Oct 2015 09:04:20 -0400 Subject: [Cdash] Problem sorting by the Time column Message-ID: In the Google Chrome browser, this page does not sort properly by the Time column: https://open.cdash.org/viewTest.php?onlypassed&buildid=4065227 Same exact misbehavior in Firefox, too. On Windows 8.1. Known problem? Thanks, David C. From zack.galbreath at kitware.com Thu Oct 22 13:35:21 2015 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Thu, 22 Oct 2015 09:35:21 -0400 Subject: [Cdash] Problem sorting by the Time column In-Reply-To: References: Message-ID: Thanks for the report. As luck would have it, I'm currently working on viewTest.php. My hope is to improve its performance when thousands of tests are present (like ITK). I'll make sure to take another look at sorting too. On Thu, Oct 22, 2015 at 9:04 AM, David Cole via Cdash < cdash at public.kitware.com> wrote: > In the Google Chrome browser, this page does not sort properly by the > Time column: > https://open.cdash.org/viewTest.php?onlypassed&buildid=4065227 > > Same exact misbehavior in Firefox, too. On Windows 8.1. > > Known problem? > > > Thanks, > David C. > _______________________________________________ > Cdash mailing list > Cdash at public.kitware.com > http://public.kitware.com/mailman/listinfo/cdash > -------------- next part -------------- An HTML attachment was scrubbed... URL: From DLRdave at aol.com Fri Oct 23 18:04:42 2015 From: DLRdave at aol.com (David Cole) Date: Fri, 23 Oct 2015 14:04:42 -0400 Subject: [CDash] [Cdash] Problem sorting by the Time column In-Reply-To: References: Message-ID: On a not unrelated note... Since this set of updates: https://open.cdash.org/viewChanges.php?project=CDash&date=2015-10-07 80+ tests are failing persistently on multiple submitters every night on the CDash dashboard. Are any of the 3 authors involved (you, Patrick Reynolds and Jamie Snape) planning to fix these test failures? Even before that, there were a handful of persistently failing tests on several dashboard submitters. I know from painful experience that it is difficult to diagnose CDash test failures sometimes, but the current state of the system would appear to be quite miserable. Only 1 out of 85 tests passes on the machine I'm submitting a dashboard from..... ?? On Thu, Oct 22, 2015 at 9:35 AM, Zack Galbreath wrote: > Thanks for the report. > > As luck would have it, I'm currently working on viewTest.php. My hope is to > improve its performance when thousands of tests are present (like ITK). > I'll make sure to take another look at sorting too. > > > > On Thu, Oct 22, 2015 at 9:04 AM, David Cole via Cdash > wrote: >> >> In the Google Chrome browser, this page does not sort properly by the >> Time column: >> https://open.cdash.org/viewTest.php?onlypassed&buildid=4065227 >> >> Same exact misbehavior in Firefox, too. On Windows 8.1. >> >> Known problem? >> >> >> Thanks, >> David C. >> _______________________________________________ >> Cdash mailing list >> Cdash at public.kitware.com >> http://public.kitware.com/mailman/listinfo/cdash > > From zack.galbreath at kitware.com Fri Oct 23 19:06:15 2015 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Fri, 23 Oct 2015 15:06:15 -0400 Subject: [CDash] [Cdash] Problem sorting by the Time column In-Reply-To: References: Message-ID: On Fri, Oct 23, 2015 at 2:04 PM, David Cole wrote: > On a not unrelated note... > > Since this set of updates: > https://open.cdash.org/viewChanges.php?project=CDash&date=2015-10-07 > > 80+ tests are failing persistently on multiple submitters every night > on the CDash dashboard. > > Are any of the 3 authors involved (you, Patrick Reynolds and Jamie > Snape) planning to fix these test failures? > This update introduced a new installation step that the site maintainers will need to perform: https://github.com/Kitware/CDash#installation Even before that, there were a handful of persistently failing tests > on several dashboard submitters. > > I know from painful experience that it is difficult to diagnose CDash > test failures sometimes, but the current state of the system would > appear to be quite miserable. Only 1 out of 85 tests passes on the > machine I'm submitting a dashboard from..... > It's true that there's still a couple flaky tests floating around, but hopefully we'll be able to fix these up. The goal is to be get trustworthy pass/fail results from CircleCI whenever a pull request is created. -------------- next part -------------- An HTML attachment was scrubbed... URL: From DLRdave at aol.com Fri Oct 23 19:40:39 2015 From: DLRdave at aol.com (David Cole) Date: Fri, 23 Oct 2015 15:40:39 -0400 Subject: [CDash] [Cdash] Problem sorting by the Time column In-Reply-To: References: Message-ID: On Fri, Oct 23, 2015 at 3:06 PM, Zack Galbreath wrote: > ... > > This update introduced a new installation step that the site maintainers > will need to perform: > > https://github.com/Kitware/CDash#installation > Perhaps an email notification to this list might have been a good idea then? ;-) > > It's true that there's still a couple flaky tests floating around, but > hopefully we'll be able to fix these up. The goal is to be get trustworthy > pass/fail results from CircleCI whenever a pull request is created. Good to know. Thanks, D From nilsgladitz at gmail.com Sat Oct 24 15:03:44 2015 From: nilsgladitz at gmail.com (Nils Gladitz) Date: Sat, 24 Oct 2015 17:03:44 +0200 Subject: [CDash] [Cdash] Problem sorting by the Time column In-Reply-To: References: Message-ID: <562B9DD0.5030903@gmail.com> On 23.10.2015 21:40, David Cole via CDash wrote: > On Fri, Oct 23, 2015 at 3:06 PM, Zack Galbreath > wrote: >> ... >> >> This update introduced a new installation step that the site maintainers >> will need to perform: >> >> https://github.com/Kitware/CDash#installation >> > Perhaps an email notification to this list might have been a good idea then? ;-) > After following the discussion here I updated my site (nibble) accordingly. My MySQL submission now mostly works (3 remaining failures) but PostgreSQL seems to be still mostly broken (80 failures). Nils From zack.galbreath at kitware.com Mon Oct 26 18:38:54 2015 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Mon, 26 Oct 2015 14:38:54 -0400 Subject: [CDash] [Cdash] Problem sorting by the Time column In-Reply-To: <562B9DD0.5030903@gmail.com> References: <562B9DD0.5030903@gmail.com> Message-ID: On Sat, Oct 24, 2015 at 11:03 AM, Nils Gladitz wrote: > After following the discussion here I updated my site (nibble) accordingly. > > My MySQL submission now mostly works (3 remaining failures) but PostgreSQL > seems to be still mostly broken (80 failures). > Thanks for taking the time to update your site. I'm also running a PostgreSQL submission (nix.kitware) and I'm not encountering the same failing tests that you are. It looks like your site is failing during the install test, but further details are scarce. If you get a chance, could you see if there's any relevant details in any of the error logs (CDash/PHP/postgres)? -------------- next part -------------- An HTML attachment was scrubbed... URL: From nilsgladitz at gmail.com Mon Oct 26 19:34:39 2015 From: nilsgladitz at gmail.com (Nils Gladitz) Date: Mon, 26 Oct 2015 20:34:39 +0100 Subject: [CDash] [Cdash] Problem sorting by the Time column In-Reply-To: References: <562B9DD0.5030903@gmail.com> Message-ID: <562E804F.4030804@gmail.com> On 26.10.2015 19:38, Zack Galbreath wrote: > On Sat, Oct 24, 2015 at 11:03 AM, Nils Gladitz > wrote: > > After following the discussion here I updated my site (nibble) > accordingly. > > My MySQL submission now mostly works (3 remaining failures) but > PostgreSQL seems to be still mostly broken (80 failures). > > > Thanks for taking the time to update your site. > > I'm also running a PostgreSQL submission (nix.kitware) and I'm not > encountering the same failing tests that you are. It looks like your > site is failing during the install test, but further details are > scarce. If you get a chance, could you see if there's any relevant > details in any of the error logs (CDash/PHP/postgres)? Thanks for the pointer. The install test output for my last two submissions contains: Error connecting to host postgres database. Tried names 'host' and 'postgres' Error connecting to host postgres database. Tried names 'host' and 'postgres' I tried running the install test manually from the nightly build directory where it previously failed (ctest -R install -V) but this time it ran fine. Running all tests I even got to "15 tests failed out of 97". I also run a submission for "Release-2-2-2" with PostgreSQL from the same machine and it also does not show those issues. I have no idea what is going on there. Nils -------------- next part -------------- An HTML attachment was scrubbed... URL: From nilsgladitz at gmail.com Tue Oct 27 09:35:34 2015 From: nilsgladitz at gmail.com (Nils Gladitz) Date: Tue, 27 Oct 2015 10:35:34 +0100 Subject: [CDash] "install" test issues In-Reply-To: <562E804F.4030804@gmail.com> References: <562B9DD0.5030903@gmail.com> <562E804F.4030804@gmail.com> Message-ID: <562F4566.1000407@gmail.com> On 10/26/2015 08:34 PM, Nils Gladitz wrote: > On 26.10.2015 19:38, Zack Galbreath wrote: >> >> >> I'm also running a PostgreSQL submission (nix.kitware) and I'm not >> encountering the same failing tests that you are. It looks like your >> site is failing during the install test, but further details are >> scarce. If you get a chance, could you see if there's any relevant >> details in any of the error logs (CDash/PHP/postgres)? > > I have no idea what is going on there I set up a new instance on a different machine for testing. One issue I found seems to be https://github.com/Kitware/CDash/blob/master/install.php#L114 which in my case resulted in 'database "cdash" does not exist'. I think it tries the "cdash" database here because no database name was given and "cdash" happens to be the name of my database user; I assume it was working for you because in your case there was an existing database with the name of your user(?) pdo_select_db("$CDASH_DB_NAME") seems to help in my case but I don't know if that is the correct fix. On a somewhat related note the "install" test seems to falsely pass when using a user without database creation privileges: test 1 Start 1: install 1: Test command: /usr/bin/php "/var/www/html/CDash/tests/singletest.php" "/var/www/html/CDash/tests/test_install.php" 1: Test timeout computed to be: 1500 1: /var/www/html/CDash/tests/test_install.php 1: All Tests 1: Error connecting to host postgres database. 1: Tried names 'host' and 'postgres' 1: Error connecting to host postgres database. 1: Tried names 'host' and 'postgres' 1: Error File: /var/www/html/CDash/tests/test_install.php on line: 34: error query(CREATE DATABASE) 1/1 Test #1: install .......................... Passed 0.08 sec The following tests passed: install Nils -------------- next part -------------- An HTML attachment was scrubbed... URL: