Re: [Boost-cmake] Labels for known failures

On May 19, 2009, at 7:27 AM, David Cole wrote: On Mon, May 18, 2009 at 3:50 PM, Brad King wrote: Michael Jackson wrote: thanks for the heads up about vxl. I took those 2 scripts and adapted them for boost. I have since been able to submit an experimental Dashboard to

Re: [Boost-cmake] Labels for known failures

On Tue, May 19, 2009 at 9:30 AM, Michael Jackson < mike.jack...@bluequartz.net> wrote: > I am having some trouble wrapping my head around what exactly is meant by: > > GetLogicalProcessorsPerPhysical > > Is that logical per core, per CPU or what? Right now I calculate the value > based on the num

Re: [Boost-cmake] Labels for known failures

David, I am having some trouble wrapping my head around what exactly is meant by: GetLogicalProcessorsPerPhysical Is that logical per core, per CPU or what? Right now I calculate the value based on the number of logical and physical. So for my Xeon with HyperThreading I get a value of 8.

Re: [Boost-cmake] Labels for known failures

On Tue, May 19, 2009 at 7:27 AM, David Cole wrote: > On Mon, May 18, 2009 at 3:50 PM, Brad King wrote: >> >> Michael Jackson wrote: >>> >>>  thanks for the heads up about vxl. I took those 2 scripts and adapted >>> them for boost. I have since been able to submit an experimental Dashboard >>> to

Re: [Boost-cmake] Labels for known failures

On Mon, May 18, 2009 at 3:50 PM, Brad King wrote: > Michael Jackson wrote: > >> thanks for the heads up about vxl. I took those 2 scripts and adapted >> them for boost. I have since been able to submit an experimental Dashboard >> to . Lo

Re: [Boost-cmake] Labels for known failures

Michael Jackson wrote: thanks for the heads up about vxl. I took those 2 scripts and adapted them for boost. I have since been able to submit an experimental Dashboard to . Look for f...@bluequartz.net - the one that actually ran all t

Re: [Boost-cmake] Labels for known failures

_ Mike Jackson mike.jack...@bluequartz.net BlueQuartz Softwarewww.bluequartz.net Principal Software Engineer Dayton, Ohio On May 18, 2009, at 11:19 AM, Brad King wrote: troy d. stras

Re: [Boost-cmake] Labels for known failures

Michael Jackson wrote: [ snip lots of code ] So I can have a cron task just run the first shell script and I can submit a dashboard with all the options that I want. Again, Not sure if that helps explain anything or not. Just posting as an example. Would you be willing to have a go at

Re: [Boost-cmake] Labels for known failures

On May 18, 2009, at 12:08 PM, Brad King wrote: troy d. straszheim wrote: Question #1: How do the settings in the script you posted relate to the settings found in $CMAKE_SOURCE_DIR/CTestConfig.cmake? Can they be combined? The settings in the source tree are project-wide and have CDash

Re: [Boost-cmake] Labels for known failures

troy d. straszheim wrote: Question #1: How do the settings in the script you posted relate to the settings found in $CMAKE_SOURCE_DIR/CTestConfig.cmake? Can they be combined? The settings in the source tree are project-wide and have CDash submission information. These are shared by all subm

Re: [Boost-cmake] Labels for known failures

Brad King wrote: The script can be written totally outside the source and build trees. If written properly it can do the initial checkout and create the build tree. A standalone script I use to do one of CMake's builds appears below. You can also create project-specific helper scripts like this

Re: [Boost-cmake] Labels for known failures

troy d. straszheim wrote: I've had a fair amount of difficulty getting ctest scripts to work. The best I've been able to come up with is 1. Configure a build space with cmake -DBUILD_REGRESSION_TESTS=ON 1a. Customize as necessary 2. Run ctest -D Whatever I've played with having cmake try to c

Re: [Boost-cmake] Labels for known failures

Brad King wrote: troy d. straszheim wrote: Doug Gregor wrote: Note that, for these labels to work, the tester needs to be running CMake 2.7.x (which is currently in CMake CVS but isn't yet an official release). This is pretty important, because labels are also going to be used to give the libr

Re: [Boost-cmake] Labels for known failures

troy d. straszheim wrote: Doug Gregor wrote: Note that, for these labels to work, the tester needs to be running CMake 2.7.x (which is currently in CMake CVS but isn't yet an official release). This is pretty important, because labels are also going to be used to give the library-centric view o

Re: [Boost-cmake] Labels for known failures

On Fri, May 15, 2009 at 2:31 PM, troy d. straszheim wrote: > Doug Gregor wrote: >> >> Note that, for these labels to work, the tester needs to be running >> CMake 2.7.x (which is currently in CMake CVS but isn't yet an official >> release). This is pretty important, because labels are also going t

Re: [Boost-cmake] Labels for known failures

Doug Gregor wrote: Note that, for these labels to work, the tester needs to be running CMake 2.7.x (which is currently in CMake CVS but isn't yet an official release). This is pretty important, because labels are also going to be used to give the library-centric view of the dashboard. Nifty..

Re: [Boost-cmake] Labels for known failures

CDash does not have filters on the viewTest page yet, but it is planned for a future CDash release. It's cool to see somebody using labels already... Nice job, Doug! David Cole Kitware, Inc. On Fri, May 15, 2009 at 12:54 AM, Doug Gregor wrote: > I've added the ability to mark up known failur

[Boost-cmake] Labels for known failures

I've added the ability to mark up known failures in the regression tests directly in the CMake files for those tests. For example, here's one such description of known failures: boost_test_run(optional_test_ref KNOWN_FAILURES "gcc-4.[0-3].[0-9]-.*") The boost_test_run macro use creates the