[CMake] turning inverting dashboard interpretation of FATAL_ERRORs at cmake

Matthias Kretz kretz at kde.org
Fri May 3 12:22:37 EDT 2013


On Thursday 25 April 2013 20:09:09 Alexander Neundorf wrote:
> On Thursday 25 April 2013, Matthias Kretz wrote:
> > On Thursday 25 April 2013 09:46:03 Bill Hoffman wrote:
> > > On 4/25/2013 9:15 AM, Matthias Kretz wrote:
> > > > I have several checks in my project that make cmake error out with
> > > > FATAL_ERROR. This is submitted as error to the dashboard. In reality
> > > > it
> > > > would be an error if this error would not appear - and it is the
> > > > expected result if cmake errors out. Is there a possiblity to invert
> > > > the result of the configure step for certain system setups?
> > > > 
> > > > Alternatively I'd skip the CTEST_CONFIGURE call in the ctest script
> > > > and
> > > > just submit Notes that elaborate on the abort. But that doesn't show
> > > > up
> > > > on the dashboard at all.
> > > > 
> > > > Any ideas?
> > > 
> > > Is this for an individual test?  If so, you can use the regex matching
> > > instead of return code to determine pass fail.  Would that work?
> > 
> > I'm not sure we're talking about the same thing. I'm talking about
> > ctest_configure - i.e. before build or tests. IIUC you're talking about
> > regex matching at ctest_test?
> 
> so the good result is if the configure step of your project fails ?

Exactly.

And running some cmake code in the test phase is certainly possible, but not 
what I'm looking for. It would require the configure step of my project to 
pass, disable all targets, and enable a test that doesn't do anything useful 
anymore, because the test already happened at configure time. So I could also 
simply skip that and just let configure pass + disable all targets.

-- 
________________________________________________________
Matthias Kretz (Germany)                            <><
http://kretzfamily.de/


More information about the CMake mailing list