CMake/Tests/RunCMake/Configure/ContinueAfterError-stderr.txt

^CMake Error at ContinueAfterError.cmake:[0-9]+ \(message\):
  error in loop body
Call Stack \(most recent call first\):
  ContinueAfterError.cmake:[0-9]+ \(m\)
  ContinueAfterError.cmake:[0-9]+ \(f\)
  CMakeLists.txt:[0-9]+ \(include\)
+
CMake Error at ContinueAfterError.cmake:[0-9]+ \(message\):
  error in loop body
Call Stack \(most recent call first\):
  ContinueAfterError.cmake:[0-9]+ \(m\)
  ContinueAfterError.cmake:[0-9]+ \(f\)
  CMakeLists.txt:[0-9]+ \(include\)$
cmMakefile: Restore nested error logic use of cmExecutionStatus Since commit 14a8d61f (cmMakefile: Port nested error logic away from cmExecutionStatus) we fail to continue processing function and macro bodies after non-fatal errors. A non-fatal error should not stop foreach loops, macro bodies, nested bodies, or the outer script. Add a test covering these cases, and revert the change to fix them. Also revert commit 2af853de (cmMakefile: Simplify IssueMessage implementation) because the assertion it added (which was removed by the above commit and is restored by reverting it) is incorrect. We do have code paths that call cmMakefile::IssueMessage with an empty execution stack, such as in CheckForUnusedVariables's LogUnused call. 2016-09-06 22:25:26 +03:00			`^CMake Error at ContinueAfterError.cmake:[0-9]+ \(message\):`
			`error in loop body`
			`Call Stack \(most recent call first\):`
			`ContinueAfterError.cmake:[0-9]+ \(m\)`
			`ContinueAfterError.cmake:[0-9]+ \(f\)`
			`CMakeLists.txt:[0-9]+ \(include\)`
			`+`
			`CMake Error at ContinueAfterError.cmake:[0-9]+ \(message\):`
			`error in loop body`
			`Call Stack \(most recent call first\):`
			`ContinueAfterError.cmake:[0-9]+ \(m\)`
			`ContinueAfterError.cmake:[0-9]+ \(f\)`
			`CMakeLists.txt:[0-9]+ \(include\)$`