Fix exit code for cts-runner
authorThomas Spurden <thomas.spurden@broadcom.com>
Mon, 8 Feb 2021 15:30:15 +0000 (15:30 +0000)
committerAlexander Galazin <Alexander.Galazin@arm.com>
Thu, 25 Feb 2021 18:50:03 +0000 (18:50 +0000)
The runner used m_summary.isConformant to determine the exit code after
m_summary had been cleared by TestRunner::deinit, so it was always
exiting with a failure code.

Don't clear m_summary so that isConformant is valid after deinit.

Affects:

cts-runner

Components: Framework

VK-GL-CTS issue: 1982

Change-Id: I665017f7b11985f1e639971e4a9a627045f3664a
(cherry picked from commit 0f2a50e88aad4dae6330168f01c224b3de5bb629)

external/openglcts/modules/runner/glcTestRunner.cpp

index ce2e3ab2cc6c7ca47e9fc698b9832df718fc5234..648b98110c22e6a72af1a73a37beab1a487ad3d2 100644 (file)
@@ -779,7 +779,6 @@ void TestRunner::deinit(void)
        writeRunSummary(m_summary, de::FilePath::join(m_logDirPath, "cts-run-summary.xml").getPath());
 
        m_runSessions.clear();
-       m_summary.clear();
 }
 
 void TestRunner::initSession(const TestRunParams& runParams)