From timo.reichl at web.de Thu Sep 8 11:05:33 2016 From: timo.reichl at web.de (Timo Reichl) Date: Thu, 8 Sep 2016 17:05:33 +0200 Subject: [CDash] CDash upgrade [1.8.2 => 2.3.0] corrupts Coverage View Message-ID: An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Thu Sep 8 11:38:59 2016 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Thu, 8 Sep 2016 11:38:59 -0400 Subject: [CDash] CDash upgrade [1.8.2 => 2.3.0] corrupts Coverage View In-Reply-To: References: Message-ID: On Thu, Sep 8, 2016 at 11:05 AM, Timo Reichl wrote: > Project is there, the coverage percentage aswell, but after clicking on a > specific file, there is nothing (1 empty line of code) > Line-by-line coverage is stored in the coveragefilelog table. Could you try executing a query like this? SELECT log from coveragefilelog WHERE buildid=; Whether or not anything comes back will let us know if this is a data ingestion problem or a data display problem. -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Mon Sep 12 09:44:19 2016 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Mon, 12 Sep 2016 09:44:19 -0400 Subject: [CDash] CDash upgrade [1.8.2 => 2.3.0] corrupts Coverage View In-Reply-To: References:

Message-ID: On Fri, Sep 9, 2016 at 3:09 AM, Timo Reichl wrote: > It returns 25 BLOBs containing a string splitted by ; like: > > 13:144;18:144;21:144;23:144;25:144;27:876;29:876;32:138; > 34:138;37:111;39:111;42:24;44:24;45:24;47:1;49:1;50:1;52: > 489;54:489;57:264;59:264;60:264;61:264;62:264;64:264;65: > 14;67:264;70:69;72:69;73:69;74:69;75:69;76:69;79:43;81:43; > 82:43;84:43;85:36;87:43;89:128;91:128;94:97;96:97;98:8; > 100:89;101:89;105:41;107:41;109:0;111:41;112:41;116:119; > 119:119;120:79;122:119;124:46;126:46;128:9;130:46;132:8;134: > 8;136:2;138:8;140:4;142:4;144:2;146:4;148:4;150:4;152:3;154: > 4;156:5;158:5;160:4;162:5;164:5;166:5;168:1;170:5;172:357; > 174:357;176:31;178:357;180:130;182:130;183:130;185:20; > 187:20;188:20;190:6;192:6;193:6;195:7;197:7;198:7;200:6;202: > 6;203:6;205:7;207:7;208:7;210:1;212:1;213:1;215:129;217:129; > 218:129;220:16;222:16;225:5;227:5;230:25;232:25;235:3;237: > 3;238:3;240:4;242:4;243:4;245:8;247:8;248:8;250:55;252:55; > 255:34;257:34;258:34;259:34;261:140;263:140;264:140;266: > 279;268:279;270:2;272:279;276:60; > > So I guess the info is there, but somehow CDash doesn't know how to > retrieve/parse it maybe? > That sounds right. This is just a guess, but maybe you don't have pdo_mysql enabled? We've gradually been migrating our SQL queries to use prepared statements, as this provides better protection against SQL injection vulnerabilities. To check this, make a test page (in CDash or elsewhere) that simply calls phpinfo() and navigate to it with a web browser. In the output, search for "PDO" to see if the MySQL driver is installed or enabled. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sean at rogue-research.com Mon Sep 12 13:21:33 2016 From: sean at rogue-research.com (Sean McBride) Date: Mon, 12 Sep 2016 13:21:33 -0400 Subject: [CDash] new CDash release? Message-ID: <20160912172133.1941602283@mail.rogue-research.com> Hi all, It seems to me there hasn't been a release of CDash for a year or two. open.cdash.org describes itself as 2.3.0, but the download page says 2.2.3 is newest. What's the release schedule/plan for this project? Thanks, -- ____________________________________________________________ Sean McBride, B. Eng sean at rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montr?al, Qu?bec, Canada From zack.galbreath at kitware.com Tue Sep 13 11:24:49 2016 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Tue, 13 Sep 2016 11:24:49 -0400 Subject: [CDash] new CDash release? In-Reply-To: <20160912172133.1941602283@mail.rogue-research.com> References: <20160912172133.1941602283@mail.rogue-research.com> Message-ID: On Mon, Sep 12, 2016 at 1:21 PM, Sean McBride wrote: > Hi all, > > It seems to me there hasn't been a release of CDash for a year or two. > open.cdash.org describes itself as 2.3.0, but the download page says > 2.2.3 is newest. > > What's the release schedule/plan for this project? > I plan to perform another upgrade of open.cdash.org before the end of the month. If no new bugs are reported we'll tag that version as CDash v2.4. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgfouca at sandia.gov Tue Sep 27 18:12:57 2016 From: jgfouca at sandia.gov (Foucar, James G) Date: Tue, 27 Sep 2016 22:12:57 +0000 Subject: [CDash] uploading commit info to cdash dashboard Message-ID: Hello, I'd really like to post the sha1 of the commit that was tested for an individual cdash build. I'd like to display it prominently once the build is clicked. For example, if you look here http://my.cdash.org/buildSummary.php?buildid=1056548 You'll see a number of fields that are not particularly useful to us like OS Name and OS Version. I'd like to replace or hijack one of those fields to instead display the commit id that was tested. How might I go about doing this? Thanks, -Jim -------------- next part -------------- An HTML attachment was scrubbed... URL: From DLRdave at aol.com Tue Sep 27 19:27:07 2016 From: DLRdave at aol.com (David Cole) Date: Tue, 27 Sep 2016 19:27:07 -0400 Subject: [CDash] uploading commit info to cdash dashboard In-Reply-To: References: Message-ID: It wouldn't be easy to hijack one of the fields you mentioned, but it would be fairly easy to encode the first 7 or 8 chars of the commit id into the build name. HTH, David C. > On Sep 27, 2016, at 6:12 PM, Foucar, James G wrote: > > Hello, > > I'd really like to post the sha1 of the commit that was tested for an individual cdash build. I'd like to display it prominently once the build is clicked. For example, if you look here > http://my.cdash.org/buildSummary.php?buildid=1056548 > > You'll see a number of fields that are not particularly useful to us like OS Name and OS Version. I'd like to replace or hijack one of those fields to instead display the commit id that was tested. How might I go about doing this? > > Thanks, > -Jim > _______________________________________________ > CDash mailing list > CDash at public.kitware.com > http://public.kitware.com/mailman/listinfo/cdash -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgfouca at sandia.gov Tue Sep 27 20:01:10 2016 From: jgfouca at sandia.gov (Foucar, James G) Date: Wed, 28 Sep 2016 00:01:10 +0000 Subject: [CDash] [EXTERNAL] Re: uploading commit info to cdash dashboard In-Reply-To: References:

Message-ID: <018A7C0F-82AF-42D4-A8AA-9A1909B3C9F9@sandia.gov> Would that make each build different in the eyes of CMake? Wouldn't that break the +/- feature for new fails and passes? From: David Cole Date: Tuesday, September 27, 2016 at 5:27 PM To: "Foucar, James G" Cc: "cdash at public.kitware.com" Subject: [EXTERNAL] Re: [CDash] uploading commit info to cdash dashboard It wouldn't be easy to hijack one of the fields you mentioned, but it would be fairly easy to encode the first 7 or 8 chars of the commit id into the build name. HTH, David C. On Sep 27, 2016, at 6:12 PM, Foucar, James G > wrote: Hello, I'd really like to post the sha1 of the commit that was tested for an individual cdash build. I'd like to display it prominently once the build is clicked. For example, if you look here http://my.cdash.org/buildSummary.php?buildid=1056548 You'll see a number of fields that are not particularly useful to us like OS Name and OS Version. I'd like to replace or hijack one of those fields to instead display the commit id that was tested. How might I go about doing this? Thanks, -Jim _______________________________________________ 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 Tue Sep 27 20:22:00 2016 From: DLRdave at aol.com (David Cole) Date: Tue, 27 Sep 2016 20:22:00 -0400 Subject: [CDash] [EXTERNAL] Re: uploading commit info to cdash dashboard In-Reply-To: <018A7C0F-82AF-42D4-A8AA-9A1909B3C9F9@sandia.gov> References:

<018A7C0F-82AF-42D4-A8AA-9A1909B3C9F9@sandia.gov> Message-ID: <74E7F098-BD31-46E1-8D13-EE08E4B2F423@aol.com> Yes it would. Sorry, didn't think about that part. I use this technique with primarily individual Experimental builds... David > On Sep 27, 2016, at 8:01 PM, Foucar, James G wrote: > > Would that make each build different in the eyes of CMake? Wouldn't that break the +/- feature for new fails and passes? > > From: David Cole > Date: Tuesday, September 27, 2016 at 5:27 PM > To: "Foucar, James G" > Cc: "cdash at public.kitware.com" > Subject: [EXTERNAL] Re: [CDash] uploading commit info to cdash dashboard > > It wouldn't be easy to hijack one of the fields you mentioned, but it would be fairly easy to encode the first 7 or 8 chars of the commit id into the build name. > > > HTH, > David C. > > > On Sep 27, 2016, at 6:12 PM, Foucar, James G wrote: > > Hello, > > I'd really like to post the sha1 of the commit that was tested for an individual cdash build. I'd like to display it prominently once the build is clicked. For example, if you look here > http://my.cdash.org/buildSummary.php?buildid=1056548 > > You'll see a number of fields that are not particularly useful to us like OS Name and OS Version. I'd like to replace or hijack one of those fields to instead display the commit id that was tested. How might I go about doing this? > > Thanks, > -Jim > _______________________________________________ > CDash mailing list > CDash at public.kitware.com > http://public.kitware.com/mailman/listinfo/cdash -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Wed Sep 28 09:19:50 2016 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Wed, 28 Sep 2016 09:19:50 -0400 Subject: [CDash] [EXTERNAL] Re: uploading commit info to cdash dashboard In-Reply-To: <74E7F098-BD31-46E1-8D13-EE08E4B2F423@aol.com> References:

<018A7C0F-82AF-42D4-A8AA-9A1909B3C9F9@sandia.gov> <74E7F098-BD31-46E1-8D13-EE08E4B2F423@aol.com> Message-ID: > > On Sep 27, 2016, at 6:12 PM, Foucar, James G wrote: > > I'd really like to post the sha1 of the commit that was tested for an > individual cdash build. I'd like to display it prominently once the build > is clicked. For example, if you look here > > http://my.cdash.org/buildSummary.php?buildid=1056548 > > > > You'll see a number of fields that are not particularly useful to us like > OS Name and OS Version. I'd like to replace or hijack one of those fields > to instead display the commit id that was tested. How might I go about > doing this? > > Hi Jim, This is a good idea, but I'm not sure of a way you could affect this change as a user of CDash. This isn't quite as good, but you could link to a specific commit in your online repository viewer from your build (assuming such a thing exists). To do this, create a file ending in .url whose contents is the URL that you'd like to associate with your build. Then in your CTest driver script, do: ctest_upload(FILES "/path/to/my.url") ...before calling ctest_submit(). You can see an example of this in action here: https://open.cdash.org/index.php?project=CDash&date=2016-09-28 click on the yellow brick Icon for the "link_to_github" build. Generally speaking, the information you seek is already in the CDash database (buildupdate.revision). So it shouldn't be too much work to expose this value on buildSummary.php. I'll look further into this when I get some time. In the not too distant future, I plan on replacing the "Update" column on index.php with a "Version" column when possible (any revision control system more modern than CVS). The idea being that seeing the version of the code that was built is more useful than seeing how many files changed. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgfouca at sandia.gov Wed Sep 28 12:54:36 2016 From: jgfouca at sandia.gov (Foucar, James G) Date: Wed, 28 Sep 2016 16:54:36 +0000 Subject: [CDash] [EXTERNAL] Re: uploading commit info to cdash dashboard In-Reply-To: References:

<018A7C0F-82AF-42D4-A8AA-9A1909B3C9F9@sandia.gov> <74E7F098-BD31-46E1-8D13-EE08E4B2F423@aol.com> Message-ID: <76A5A587-20DD-46C4-A390-5312E82CE0A3@sandia.gov> Thanks, that sounds like a good change. From: Zack Galbreath Date: Wednesday, September 28, 2016 at 7:19 AM To: David Cole Cc: "Foucar, James G" , "cdash at public.kitware.com" Subject: Re: [CDash] [EXTERNAL] Re: uploading commit info to cdash dashboard On Sep 27, 2016, at 6:12 PM, Foucar, James G > wrote: I'd really like to post the sha1 of the commit that was tested for an individual cdash build. I'd like to display it prominently once the build is clicked. For example, if you look here http://my.cdash.org/buildSummary.php?buildid=1056548 You'll see a number of fields that are not particularly useful to us like OS Name and OS Version. I'd like to replace or hijack one of those fields to instead display the commit id that was tested. How might I go about doing this? Hi Jim, This is a good idea, but I'm not sure of a way you could affect this change as a user of CDash. This isn't quite as good, but you could link to a specific commit in your online repository viewer from your build (assuming such a thing exists). To do this, create a file ending in .url whose contents is the URL that you'd like to associate with your build. Then in your CTest driver script, do: ctest_upload(FILES "/path/to/my.url") ...before calling ctest_submit(). You can see an example of this in action here: https://open.cdash.org/index.php?project=CDash&date=2016-09-28 click on the yellow brick Icon for the "link_to_github" build. Generally speaking, the information you seek is already in the CDash database (buildupdate.revision). So it shouldn't be too much work to expose this value on buildSummary.php. I'll look further into this when I get some time. In the not too distant future, I plan on replacing the "Update" column on index.php with a "Version" column when possible (any revision control system more modern than CVS). The idea being that seeing the version of the code that was built is more useful than seeing how many files changed. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mdrahos at aurisrobotics.com Thu Sep 29 23:01:32 2016 From: mdrahos at aurisrobotics.com (Miroslav Drahos) Date: Fri, 30 Sep 2016 03:01:32 +0000 Subject: [CDash] Continuous doesn't run, but Experimental is fine Message-ID: Hi, I've been puzzled by the recent behavior I've been experiencing with cmake/ctest 3.2.2 on Ubuntu Linux. The Continuous target stopped working, although Experimental works fine. This is a recent development, I have had Continuous running fine for several months. Now something changed and I can't put a finger on it.... Here are some more details: ctest -VV -D ContinuousStart # output as expected, reports it created a new tag, Testing/TAG shows a new tag and Continuous ctest -VV -D ContinuousBuild # cmake was already run, so this should build, but it doesn't: UpdateCTestConfiguration from :/path/to/Release/DartConfiguration.tcl Parse Config file:/path/to/Release/DartConfiguration.tcl Site: ASR-163 Build name: Linux-gcc4.9-Release Add coverage exclude regular expressions. Add coverage exclude: .*/CMakeFiles/CMakeTmp/.* Add coverage exclude: .*/moc_.* Add coverage exclude: .*/ui_.* Add coverage exclude: .*/Testing/.* SetCTestConfiguration:CMakeCommand:/usr/bin/cmake That's all the output I get. Nothing is built, no new file in Testing, Testing/TAG is still the same, no other file/directory in Testing is created. ctest -VV -D ContinousSubmit # nothing is submitted. In contrast, Experimental does everything as expected. ExperimentalBuild builds, creates Testing/20160930-XXXX directory with Build.xml, ExperimentalSubmit target submits. What can be wrong? DartConfiguration.tcl seems ok, showing # Commands for the build/test/submit cycle ConfigureCommand: "/usr/bin/cmake" "/path/to/project" MakeCommand: /usr/bin/cmake --build . --config "${CTEST_CONFIGURATION_TYPE}" DefaultCTestConfigurationType: Release Any ideas/hints? Thank you! Miro -------------- next part -------------- An HTML attachment was scrubbed... URL: From timo.reichl at web.de Thu Sep 8 15:05:33 2016 From: timo.reichl at web.de (Timo Reichl) Date: Thu, 8 Sep 2016 17:05:33 +0200 Subject: [CDash] CDash upgrade [1.8.2 => 2.3.0] corrupts Coverage View Message-ID: An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Thu Sep 8 15:38:59 2016 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Thu, 8 Sep 2016 11:38:59 -0400 Subject: [CDash] CDash upgrade [1.8.2 => 2.3.0] corrupts Coverage View In-Reply-To: References: Message-ID: On Thu, Sep 8, 2016 at 11:05 AM, Timo Reichl wrote: > Project is there, the coverage percentage aswell, but after clicking on a > specific file, there is nothing (1 empty line of code) > Line-by-line coverage is stored in the coveragefilelog table. Could you try executing a query like this? SELECT log from coveragefilelog WHERE buildid=; Whether or not anything comes back will let us know if this is a data ingestion problem or a data display problem. -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Mon Sep 12 13:44:19 2016 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Mon, 12 Sep 2016 09:44:19 -0400 Subject: [CDash] CDash upgrade [1.8.2 => 2.3.0] corrupts Coverage View In-Reply-To: References:

Message-ID: On Fri, Sep 9, 2016 at 3:09 AM, Timo Reichl wrote: > It returns 25 BLOBs containing a string splitted by ; like: > > 13:144;18:144;21:144;23:144;25:144;27:876;29:876;32:138; > 34:138;37:111;39:111;42:24;44:24;45:24;47:1;49:1;50:1;52: > 489;54:489;57:264;59:264;60:264;61:264;62:264;64:264;65: > 14;67:264;70:69;72:69;73:69;74:69;75:69;76:69;79:43;81:43; > 82:43;84:43;85:36;87:43;89:128;91:128;94:97;96:97;98:8; > 100:89;101:89;105:41;107:41;109:0;111:41;112:41;116:119; > 119:119;120:79;122:119;124:46;126:46;128:9;130:46;132:8;134: > 8;136:2;138:8;140:4;142:4;144:2;146:4;148:4;150:4;152:3;154: > 4;156:5;158:5;160:4;162:5;164:5;166:5;168:1;170:5;172:357; > 174:357;176:31;178:357;180:130;182:130;183:130;185:20; > 187:20;188:20;190:6;192:6;193:6;195:7;197:7;198:7;200:6;202: > 6;203:6;205:7;207:7;208:7;210:1;212:1;213:1;215:129;217:129; > 218:129;220:16;222:16;225:5;227:5;230:25;232:25;235:3;237: > 3;238:3;240:4;242:4;243:4;245:8;247:8;248:8;250:55;252:55; > 255:34;257:34;258:34;259:34;261:140;263:140;264:140;266: > 279;268:279;270:2;272:279;276:60; > > So I guess the info is there, but somehow CDash doesn't know how to > retrieve/parse it maybe? > That sounds right. This is just a guess, but maybe you don't have pdo_mysql enabled? We've gradually been migrating our SQL queries to use prepared statements, as this provides better protection against SQL injection vulnerabilities. To check this, make a test page (in CDash or elsewhere) that simply calls phpinfo() and navigate to it with a web browser. In the output, search for "PDO" to see if the MySQL driver is installed or enabled. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sean at rogue-research.com Mon Sep 12 17:21:33 2016 From: sean at rogue-research.com (Sean McBride) Date: Mon, 12 Sep 2016 13:21:33 -0400 Subject: [CDash] new CDash release? Message-ID: <20160912172133.1941602283@mail.rogue-research.com> Hi all, It seems to me there hasn't been a release of CDash for a year or two. open.cdash.org describes itself as 2.3.0, but the download page says 2.2.3 is newest. What's the release schedule/plan for this project? Thanks, -- ____________________________________________________________ Sean McBride, B. Eng sean at rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montr?al, Qu?bec, Canada From zack.galbreath at kitware.com Tue Sep 13 15:24:49 2016 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Tue, 13 Sep 2016 11:24:49 -0400 Subject: [CDash] new CDash release? In-Reply-To: <20160912172133.1941602283@mail.rogue-research.com> References: <20160912172133.1941602283@mail.rogue-research.com> Message-ID: On Mon, Sep 12, 2016 at 1:21 PM, Sean McBride wrote: > Hi all, > > It seems to me there hasn't been a release of CDash for a year or two. > open.cdash.org describes itself as 2.3.0, but the download page says > 2.2.3 is newest. > > What's the release schedule/plan for this project? > I plan to perform another upgrade of open.cdash.org before the end of the month. If no new bugs are reported we'll tag that version as CDash v2.4. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgfouca at sandia.gov Tue Sep 27 22:12:57 2016 From: jgfouca at sandia.gov (Foucar, James G) Date: Tue, 27 Sep 2016 22:12:57 +0000 Subject: [CDash] uploading commit info to cdash dashboard Message-ID: Hello, I'd really like to post the sha1 of the commit that was tested for an individual cdash build. I'd like to display it prominently once the build is clicked. For example, if you look here http://my.cdash.org/buildSummary.php?buildid=1056548 You'll see a number of fields that are not particularly useful to us like OS Name and OS Version. I'd like to replace or hijack one of those fields to instead display the commit id that was tested. How might I go about doing this? Thanks, -Jim -------------- next part -------------- An HTML attachment was scrubbed... URL: From DLRdave at aol.com Tue Sep 27 23:27:07 2016 From: DLRdave at aol.com (David Cole) Date: Tue, 27 Sep 2016 19:27:07 -0400 Subject: [CDash] uploading commit info to cdash dashboard In-Reply-To: References: Message-ID: It wouldn't be easy to hijack one of the fields you mentioned, but it would be fairly easy to encode the first 7 or 8 chars of the commit id into the build name. HTH, David C. > On Sep 27, 2016, at 6:12 PM, Foucar, James G wrote: > > Hello, > > I'd really like to post the sha1 of the commit that was tested for an individual cdash build. I'd like to display it prominently once the build is clicked. For example, if you look here > http://my.cdash.org/buildSummary.php?buildid=1056548 > > You'll see a number of fields that are not particularly useful to us like OS Name and OS Version. I'd like to replace or hijack one of those fields to instead display the commit id that was tested. How might I go about doing this? > > Thanks, > -Jim > _______________________________________________ > CDash mailing list > CDash at public.kitware.com > http://public.kitware.com/mailman/listinfo/cdash -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgfouca at sandia.gov Wed Sep 28 00:01:10 2016 From: jgfouca at sandia.gov (Foucar, James G) Date: Wed, 28 Sep 2016 00:01:10 +0000 Subject: [CDash] [EXTERNAL] Re: uploading commit info to cdash dashboard In-Reply-To: References:

Message-ID: <018A7C0F-82AF-42D4-A8AA-9A1909B3C9F9@sandia.gov> Would that make each build different in the eyes of CMake? Wouldn't that break the +/- feature for new fails and passes? From: David Cole Date: Tuesday, September 27, 2016 at 5:27 PM To: "Foucar, James G" Cc: "cdash at public.kitware.com" Subject: [EXTERNAL] Re: [CDash] uploading commit info to cdash dashboard It wouldn't be easy to hijack one of the fields you mentioned, but it would be fairly easy to encode the first 7 or 8 chars of the commit id into the build name. HTH, David C. On Sep 27, 2016, at 6:12 PM, Foucar, James G > wrote: Hello, I'd really like to post the sha1 of the commit that was tested for an individual cdash build. I'd like to display it prominently once the build is clicked. For example, if you look here http://my.cdash.org/buildSummary.php?buildid=1056548 You'll see a number of fields that are not particularly useful to us like OS Name and OS Version. I'd like to replace or hijack one of those fields to instead display the commit id that was tested. How might I go about doing this? Thanks, -Jim _______________________________________________ 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 Wed Sep 28 00:22:00 2016 From: DLRdave at aol.com (David Cole) Date: Tue, 27 Sep 2016 20:22:00 -0400 Subject: [CDash] [EXTERNAL] Re: uploading commit info to cdash dashboard In-Reply-To: <018A7C0F-82AF-42D4-A8AA-9A1909B3C9F9@sandia.gov> References:

<018A7C0F-82AF-42D4-A8AA-9A1909B3C9F9@sandia.gov> Message-ID: <74E7F098-BD31-46E1-8D13-EE08E4B2F423@aol.com> Yes it would. Sorry, didn't think about that part. I use this technique with primarily individual Experimental builds... David > On Sep 27, 2016, at 8:01 PM, Foucar, James G wrote: > > Would that make each build different in the eyes of CMake? Wouldn't that break the +/- feature for new fails and passes? > > From: David Cole > Date: Tuesday, September 27, 2016 at 5:27 PM > To: "Foucar, James G" > Cc: "cdash at public.kitware.com" > Subject: [EXTERNAL] Re: [CDash] uploading commit info to cdash dashboard > > It wouldn't be easy to hijack one of the fields you mentioned, but it would be fairly easy to encode the first 7 or 8 chars of the commit id into the build name. > > > HTH, > David C. > > > On Sep 27, 2016, at 6:12 PM, Foucar, James G wrote: > > Hello, > > I'd really like to post the sha1 of the commit that was tested for an individual cdash build. I'd like to display it prominently once the build is clicked. For example, if you look here > http://my.cdash.org/buildSummary.php?buildid=1056548 > > You'll see a number of fields that are not particularly useful to us like OS Name and OS Version. I'd like to replace or hijack one of those fields to instead display the commit id that was tested. How might I go about doing this? > > Thanks, > -Jim > _______________________________________________ > CDash mailing list > CDash at public.kitware.com > http://public.kitware.com/mailman/listinfo/cdash -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Wed Sep 28 13:19:50 2016 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Wed, 28 Sep 2016 09:19:50 -0400 Subject: [CDash] [EXTERNAL] Re: uploading commit info to cdash dashboard In-Reply-To: <74E7F098-BD31-46E1-8D13-EE08E4B2F423@aol.com> References:

<018A7C0F-82AF-42D4-A8AA-9A1909B3C9F9@sandia.gov> <74E7F098-BD31-46E1-8D13-EE08E4B2F423@aol.com> Message-ID: > > On Sep 27, 2016, at 6:12 PM, Foucar, James G wrote: > > I'd really like to post the sha1 of the commit that was tested for an > individual cdash build. I'd like to display it prominently once the build > is clicked. For example, if you look here > > http://my.cdash.org/buildSummary.php?buildid=1056548 > > > > You'll see a number of fields that are not particularly useful to us like > OS Name and OS Version. I'd like to replace or hijack one of those fields > to instead display the commit id that was tested. How might I go about > doing this? > > Hi Jim, This is a good idea, but I'm not sure of a way you could affect this change as a user of CDash. This isn't quite as good, but you could link to a specific commit in your online repository viewer from your build (assuming such a thing exists). To do this, create a file ending in .url whose contents is the URL that you'd like to associate with your build. Then in your CTest driver script, do: ctest_upload(FILES "/path/to/my.url") ...before calling ctest_submit(). You can see an example of this in action here: https://open.cdash.org/index.php?project=CDash&date=2016-09-28 click on the yellow brick Icon for the "link_to_github" build. Generally speaking, the information you seek is already in the CDash database (buildupdate.revision). So it shouldn't be too much work to expose this value on buildSummary.php. I'll look further into this when I get some time. In the not too distant future, I plan on replacing the "Update" column on index.php with a "Version" column when possible (any revision control system more modern than CVS). The idea being that seeing the version of the code that was built is more useful than seeing how many files changed. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgfouca at sandia.gov Wed Sep 28 16:54:36 2016 From: jgfouca at sandia.gov (Foucar, James G) Date: Wed, 28 Sep 2016 16:54:36 +0000 Subject: [CDash] [EXTERNAL] Re: uploading commit info to cdash dashboard In-Reply-To: References:

<018A7C0F-82AF-42D4-A8AA-9A1909B3C9F9@sandia.gov> <74E7F098-BD31-46E1-8D13-EE08E4B2F423@aol.com> Message-ID: <76A5A587-20DD-46C4-A390-5312E82CE0A3@sandia.gov> Thanks, that sounds like a good change. From: Zack Galbreath Date: Wednesday, September 28, 2016 at 7:19 AM To: David Cole Cc: "Foucar, James G" , "cdash at public.kitware.com" Subject: Re: [CDash] [EXTERNAL] Re: uploading commit info to cdash dashboard On Sep 27, 2016, at 6:12 PM, Foucar, James G > wrote: I'd really like to post the sha1 of the commit that was tested for an individual cdash build. I'd like to display it prominently once the build is clicked. For example, if you look here http://my.cdash.org/buildSummary.php?buildid=1056548 You'll see a number of fields that are not particularly useful to us like OS Name and OS Version. I'd like to replace or hijack one of those fields to instead display the commit id that was tested. How might I go about doing this? Hi Jim, This is a good idea, but I'm not sure of a way you could affect this change as a user of CDash. This isn't quite as good, but you could link to a specific commit in your online repository viewer from your build (assuming such a thing exists). To do this, create a file ending in .url whose contents is the URL that you'd like to associate with your build. Then in your CTest driver script, do: ctest_upload(FILES "/path/to/my.url") ...before calling ctest_submit(). You can see an example of this in action here: https://open.cdash.org/index.php?project=CDash&date=2016-09-28 click on the yellow brick Icon for the "link_to_github" build. Generally speaking, the information you seek is already in the CDash database (buildupdate.revision). So it shouldn't be too much work to expose this value on buildSummary.php. I'll look further into this when I get some time. In the not too distant future, I plan on replacing the "Update" column on index.php with a "Version" column when possible (any revision control system more modern than CVS). The idea being that seeing the version of the code that was built is more useful than seeing how many files changed. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mdrahos at aurisrobotics.com Fri Sep 30 03:01:32 2016 From: mdrahos at aurisrobotics.com (Miroslav Drahos) Date: Fri, 30 Sep 2016 03:01:32 +0000 Subject: [CDash] Continuous doesn't run, but Experimental is fine Message-ID: Hi, I've been puzzled by the recent behavior I've been experiencing with cmake/ctest 3.2.2 on Ubuntu Linux. The Continuous target stopped working, although Experimental works fine. This is a recent development, I have had Continuous running fine for several months. Now something changed and I can't put a finger on it.... Here are some more details: ctest -VV -D ContinuousStart # output as expected, reports it created a new tag, Testing/TAG shows a new tag and Continuous ctest -VV -D ContinuousBuild # cmake was already run, so this should build, but it doesn't: UpdateCTestConfiguration from :/path/to/Release/DartConfiguration.tcl Parse Config file:/path/to/Release/DartConfiguration.tcl Site: ASR-163 Build name: Linux-gcc4.9-Release Add coverage exclude regular expressions. Add coverage exclude: .*/CMakeFiles/CMakeTmp/.* Add coverage exclude: .*/moc_.* Add coverage exclude: .*/ui_.* Add coverage exclude: .*/Testing/.* SetCTestConfiguration:CMakeCommand:/usr/bin/cmake That's all the output I get. Nothing is built, no new file in Testing, Testing/TAG is still the same, no other file/directory in Testing is created. ctest -VV -D ContinousSubmit # nothing is submitted. In contrast, Experimental does everything as expected. ExperimentalBuild builds, creates Testing/20160930-XXXX directory with Build.xml, ExperimentalSubmit target submits. What can be wrong? DartConfiguration.tcl seems ok, showing # Commands for the build/test/submit cycle ConfigureCommand: "/usr/bin/cmake" "/path/to/project" MakeCommand: /usr/bin/cmake --build . --config "${CTEST_CONFIGURATION_TYPE}" DefaultCTestConfigurationType: Release Any ideas/hints? Thank you! Miro -------------- next part -------------- An HTML attachment was scrubbed... URL: From timo.reichl at web.de Thu Sep 8 15:05:33 2016 From: timo.reichl at web.de (Timo Reichl) Date: Thu, 8 Sep 2016 17:05:33 +0200 Subject: [CDash] CDash upgrade [1.8.2 => 2.3.0] corrupts Coverage View Message-ID: An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Thu Sep 8 15:38:59 2016 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Thu, 8 Sep 2016 11:38:59 -0400 Subject: [CDash] CDash upgrade [1.8.2 => 2.3.0] corrupts Coverage View In-Reply-To: References: Message-ID: On Thu, Sep 8, 2016 at 11:05 AM, Timo Reichl wrote: > Project is there, the coverage percentage aswell, but after clicking on a > specific file, there is nothing (1 empty line of code) > Line-by-line coverage is stored in the coveragefilelog table. Could you try executing a query like this? SELECT log from coveragefilelog WHERE buildid=; Whether or not anything comes back will let us know if this is a data ingestion problem or a data display problem. -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Mon Sep 12 13:44:19 2016 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Mon, 12 Sep 2016 09:44:19 -0400 Subject: [CDash] CDash upgrade [1.8.2 => 2.3.0] corrupts Coverage View In-Reply-To: References:

Message-ID: On Fri, Sep 9, 2016 at 3:09 AM, Timo Reichl wrote: > It returns 25 BLOBs containing a string splitted by ; like: > > 13:144;18:144;21:144;23:144;25:144;27:876;29:876;32:138; > 34:138;37:111;39:111;42:24;44:24;45:24;47:1;49:1;50:1;52: > 489;54:489;57:264;59:264;60:264;61:264;62:264;64:264;65: > 14;67:264;70:69;72:69;73:69;74:69;75:69;76:69;79:43;81:43; > 82:43;84:43;85:36;87:43;89:128;91:128;94:97;96:97;98:8; > 100:89;101:89;105:41;107:41;109:0;111:41;112:41;116:119; > 119:119;120:79;122:119;124:46;126:46;128:9;130:46;132:8;134: > 8;136:2;138:8;140:4;142:4;144:2;146:4;148:4;150:4;152:3;154: > 4;156:5;158:5;160:4;162:5;164:5;166:5;168:1;170:5;172:357; > 174:357;176:31;178:357;180:130;182:130;183:130;185:20; > 187:20;188:20;190:6;192:6;193:6;195:7;197:7;198:7;200:6;202: > 6;203:6;205:7;207:7;208:7;210:1;212:1;213:1;215:129;217:129; > 218:129;220:16;222:16;225:5;227:5;230:25;232:25;235:3;237: > 3;238:3;240:4;242:4;243:4;245:8;247:8;248:8;250:55;252:55; > 255:34;257:34;258:34;259:34;261:140;263:140;264:140;266: > 279;268:279;270:2;272:279;276:60; > > So I guess the info is there, but somehow CDash doesn't know how to > retrieve/parse it maybe? > That sounds right. This is just a guess, but maybe you don't have pdo_mysql enabled? We've gradually been migrating our SQL queries to use prepared statements, as this provides better protection against SQL injection vulnerabilities. To check this, make a test page (in CDash or elsewhere) that simply calls phpinfo() and navigate to it with a web browser. In the output, search for "PDO" to see if the MySQL driver is installed or enabled. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sean at rogue-research.com Mon Sep 12 17:21:33 2016 From: sean at rogue-research.com (Sean McBride) Date: Mon, 12 Sep 2016 13:21:33 -0400 Subject: [CDash] new CDash release? Message-ID: <20160912172133.1941602283@mail.rogue-research.com> Hi all, It seems to me there hasn't been a release of CDash for a year or two. open.cdash.org describes itself as 2.3.0, but the download page says 2.2.3 is newest. What's the release schedule/plan for this project? Thanks, -- ____________________________________________________________ Sean McBride, B. Eng sean at rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montr?al, Qu?bec, Canada From zack.galbreath at kitware.com Tue Sep 13 15:24:49 2016 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Tue, 13 Sep 2016 11:24:49 -0400 Subject: [CDash] new CDash release? In-Reply-To: <20160912172133.1941602283@mail.rogue-research.com> References: <20160912172133.1941602283@mail.rogue-research.com> Message-ID: On Mon, Sep 12, 2016 at 1:21 PM, Sean McBride wrote: > Hi all, > > It seems to me there hasn't been a release of CDash for a year or two. > open.cdash.org describes itself as 2.3.0, but the download page says > 2.2.3 is newest. > > What's the release schedule/plan for this project? > I plan to perform another upgrade of open.cdash.org before the end of the month. If no new bugs are reported we'll tag that version as CDash v2.4. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgfouca at sandia.gov Tue Sep 27 22:12:57 2016 From: jgfouca at sandia.gov (Foucar, James G) Date: Tue, 27 Sep 2016 22:12:57 +0000 Subject: [CDash] uploading commit info to cdash dashboard Message-ID: Hello, I'd really like to post the sha1 of the commit that was tested for an individual cdash build. I'd like to display it prominently once the build is clicked. For example, if you look here http://my.cdash.org/buildSummary.php?buildid=1056548 You'll see a number of fields that are not particularly useful to us like OS Name and OS Version. I'd like to replace or hijack one of those fields to instead display the commit id that was tested. How might I go about doing this? Thanks, -Jim -------------- next part -------------- An HTML attachment was scrubbed... URL: From DLRdave at aol.com Tue Sep 27 23:27:07 2016 From: DLRdave at aol.com (David Cole) Date: Tue, 27 Sep 2016 19:27:07 -0400 Subject: [CDash] uploading commit info to cdash dashboard In-Reply-To: References: Message-ID: It wouldn't be easy to hijack one of the fields you mentioned, but it would be fairly easy to encode the first 7 or 8 chars of the commit id into the build name. HTH, David C. > On Sep 27, 2016, at 6:12 PM, Foucar, James G wrote: > > Hello, > > I'd really like to post the sha1 of the commit that was tested for an individual cdash build. I'd like to display it prominently once the build is clicked. For example, if you look here > http://my.cdash.org/buildSummary.php?buildid=1056548 > > You'll see a number of fields that are not particularly useful to us like OS Name and OS Version. I'd like to replace or hijack one of those fields to instead display the commit id that was tested. How might I go about doing this? > > Thanks, > -Jim > _______________________________________________ > CDash mailing list > CDash at public.kitware.com > http://public.kitware.com/mailman/listinfo/cdash -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgfouca at sandia.gov Wed Sep 28 00:01:10 2016 From: jgfouca at sandia.gov (Foucar, James G) Date: Wed, 28 Sep 2016 00:01:10 +0000 Subject: [CDash] [EXTERNAL] Re: uploading commit info to cdash dashboard In-Reply-To: References:

Message-ID: <018A7C0F-82AF-42D4-A8AA-9A1909B3C9F9@sandia.gov> Would that make each build different in the eyes of CMake? Wouldn't that break the +/- feature for new fails and passes? From: David Cole Date: Tuesday, September 27, 2016 at 5:27 PM To: "Foucar, James G" Cc: "cdash at public.kitware.com" Subject: [EXTERNAL] Re: [CDash] uploading commit info to cdash dashboard It wouldn't be easy to hijack one of the fields you mentioned, but it would be fairly easy to encode the first 7 or 8 chars of the commit id into the build name. HTH, David C. On Sep 27, 2016, at 6:12 PM, Foucar, James G > wrote: Hello, I'd really like to post the sha1 of the commit that was tested for an individual cdash build. I'd like to display it prominently once the build is clicked. For example, if you look here http://my.cdash.org/buildSummary.php?buildid=1056548 You'll see a number of fields that are not particularly useful to us like OS Name and OS Version. I'd like to replace or hijack one of those fields to instead display the commit id that was tested. How might I go about doing this? Thanks, -Jim _______________________________________________ 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 Wed Sep 28 00:22:00 2016 From: DLRdave at aol.com (David Cole) Date: Tue, 27 Sep 2016 20:22:00 -0400 Subject: [CDash] [EXTERNAL] Re: uploading commit info to cdash dashboard In-Reply-To: <018A7C0F-82AF-42D4-A8AA-9A1909B3C9F9@sandia.gov> References:

<018A7C0F-82AF-42D4-A8AA-9A1909B3C9F9@sandia.gov> Message-ID: <74E7F098-BD31-46E1-8D13-EE08E4B2F423@aol.com> Yes it would. Sorry, didn't think about that part. I use this technique with primarily individual Experimental builds... David > On Sep 27, 2016, at 8:01 PM, Foucar, James G wrote: > > Would that make each build different in the eyes of CMake? Wouldn't that break the +/- feature for new fails and passes? > > From: David Cole > Date: Tuesday, September 27, 2016 at 5:27 PM > To: "Foucar, James G" > Cc: "cdash at public.kitware.com" > Subject: [EXTERNAL] Re: [CDash] uploading commit info to cdash dashboard > > It wouldn't be easy to hijack one of the fields you mentioned, but it would be fairly easy to encode the first 7 or 8 chars of the commit id into the build name. > > > HTH, > David C. > > > On Sep 27, 2016, at 6:12 PM, Foucar, James G wrote: > > Hello, > > I'd really like to post the sha1 of the commit that was tested for an individual cdash build. I'd like to display it prominently once the build is clicked. For example, if you look here > http://my.cdash.org/buildSummary.php?buildid=1056548 > > You'll see a number of fields that are not particularly useful to us like OS Name and OS Version. I'd like to replace or hijack one of those fields to instead display the commit id that was tested. How might I go about doing this? > > Thanks, > -Jim > _______________________________________________ > CDash mailing list > CDash at public.kitware.com > http://public.kitware.com/mailman/listinfo/cdash -------------- next part -------------- An HTML attachment was scrubbed... URL: From zack.galbreath at kitware.com Wed Sep 28 13:19:50 2016 From: zack.galbreath at kitware.com (Zack Galbreath) Date: Wed, 28 Sep 2016 09:19:50 -0400 Subject: [CDash] [EXTERNAL] Re: uploading commit info to cdash dashboard In-Reply-To: <74E7F098-BD31-46E1-8D13-EE08E4B2F423@aol.com> References:

<018A7C0F-82AF-42D4-A8AA-9A1909B3C9F9@sandia.gov> <74E7F098-BD31-46E1-8D13-EE08E4B2F423@aol.com> Message-ID: > > On Sep 27, 2016, at 6:12 PM, Foucar, James G wrote: > > I'd really like to post the sha1 of the commit that was tested for an > individual cdash build. I'd like to display it prominently once the build > is clicked. For example, if you look here > > http://my.cdash.org/buildSummary.php?buildid=1056548 > > > > You'll see a number of fields that are not particularly useful to us like > OS Name and OS Version. I'd like to replace or hijack one of those fields > to instead display the commit id that was tested. How might I go about > doing this? > > Hi Jim, This is a good idea, but I'm not sure of a way you could affect this change as a user of CDash. This isn't quite as good, but you could link to a specific commit in your online repository viewer from your build (assuming such a thing exists). To do this, create a file ending in .url whose contents is the URL that you'd like to associate with your build. Then in your CTest driver script, do: ctest_upload(FILES "/path/to/my.url") ...before calling ctest_submit(). You can see an example of this in action here: https://open.cdash.org/index.php?project=CDash&date=2016-09-28 click on the yellow brick Icon for the "link_to_github" build. Generally speaking, the information you seek is already in the CDash database (buildupdate.revision). So it shouldn't be too much work to expose this value on buildSummary.php. I'll look further into this when I get some time. In the not too distant future, I plan on replacing the "Update" column on index.php with a "Version" column when possible (any revision control system more modern than CVS). The idea being that seeing the version of the code that was built is more useful than seeing how many files changed. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgfouca at sandia.gov Wed Sep 28 16:54:36 2016 From: jgfouca at sandia.gov (Foucar, James G) Date: Wed, 28 Sep 2016 16:54:36 +0000 Subject: [CDash] [EXTERNAL] Re: uploading commit info to cdash dashboard In-Reply-To: References:

<018A7C0F-82AF-42D4-A8AA-9A1909B3C9F9@sandia.gov> <74E7F098-BD31-46E1-8D13-EE08E4B2F423@aol.com> Message-ID: <76A5A587-20DD-46C4-A390-5312E82CE0A3@sandia.gov> Thanks, that sounds like a good change. From: Zack Galbreath Date: Wednesday, September 28, 2016 at 7:19 AM To: David Cole Cc: "Foucar, James G" , "cdash at public.kitware.com" Subject: Re: [CDash] [EXTERNAL] Re: uploading commit info to cdash dashboard On Sep 27, 2016, at 6:12 PM, Foucar, James G > wrote: I'd really like to post the sha1 of the commit that was tested for an individual cdash build. I'd like to display it prominently once the build is clicked. For example, if you look here http://my.cdash.org/buildSummary.php?buildid=1056548 You'll see a number of fields that are not particularly useful to us like OS Name and OS Version. I'd like to replace or hijack one of those fields to instead display the commit id that was tested. How might I go about doing this? Hi Jim, This is a good idea, but I'm not sure of a way you could affect this change as a user of CDash. This isn't quite as good, but you could link to a specific commit in your online repository viewer from your build (assuming such a thing exists). To do this, create a file ending in .url whose contents is the URL that you'd like to associate with your build. Then in your CTest driver script, do: ctest_upload(FILES "/path/to/my.url") ...before calling ctest_submit(). You can see an example of this in action here: https://open.cdash.org/index.php?project=CDash&date=2016-09-28 click on the yellow brick Icon for the "link_to_github" build. Generally speaking, the information you seek is already in the CDash database (buildupdate.revision). So it shouldn't be too much work to expose this value on buildSummary.php. I'll look further into this when I get some time. In the not too distant future, I plan on replacing the "Update" column on index.php with a "Version" column when possible (any revision control system more modern than CVS). The idea being that seeing the version of the code that was built is more useful than seeing how many files changed. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mdrahos at aurisrobotics.com Fri Sep 30 03:01:32 2016 From: mdrahos at aurisrobotics.com (Miroslav Drahos) Date: Fri, 30 Sep 2016 03:01:32 +0000 Subject: [CDash] Continuous doesn't run, but Experimental is fine Message-ID: Hi, I've been puzzled by the recent behavior I've been experiencing with cmake/ctest 3.2.2 on Ubuntu Linux. The Continuous target stopped working, although Experimental works fine. This is a recent development, I have had Continuous running fine for several months. Now something changed and I can't put a finger on it.... Here are some more details: ctest -VV -D ContinuousStart # output as expected, reports it created a new tag, Testing/TAG shows a new tag and Continuous ctest -VV -D ContinuousBuild # cmake was already run, so this should build, but it doesn't: UpdateCTestConfiguration from :/path/to/Release/DartConfiguration.tcl Parse Config file:/path/to/Release/DartConfiguration.tcl Site: ASR-163 Build name: Linux-gcc4.9-Release Add coverage exclude regular expressions. Add coverage exclude: .*/CMakeFiles/CMakeTmp/.* Add coverage exclude: .*/moc_.* Add coverage exclude: .*/ui_.* Add coverage exclude: .*/Testing/.* SetCTestConfiguration:CMakeCommand:/usr/bin/cmake That's all the output I get. Nothing is built, no new file in Testing, Testing/TAG is still the same, no other file/directory in Testing is created. ctest -VV -D ContinousSubmit # nothing is submitted. In contrast, Experimental does everything as expected. ExperimentalBuild builds, creates Testing/20160930-XXXX directory with Build.xml, ExperimentalSubmit target submits. What can be wrong? DartConfiguration.tcl seems ok, showing # Commands for the build/test/submit cycle ConfigureCommand: "/usr/bin/cmake" "/path/to/project" MakeCommand: /usr/bin/cmake --build . --config "${CTEST_CONFIGURATION_TYPE}" DefaultCTestConfigurationType: Release Any ideas/hints? Thank you! Miro -------------- next part -------------- An HTML attachment was scrubbed... URL: