From 0f503a9147aa5c58d42168dc2b4e8b520971e438 Mon Sep 17 00:00:00 2001
From: Josh Lehan <krellan@google.com>
Date: Wed, 16 Mar 2022 16:01:08 -0700
Subject: README: Fix coverage instructions

They must run as two separate steps, otherwise the coverage process will
run before the test process completes, resulting in corrupted output.

Tested: Now it works for me.

Signed-off-by: Josh Lehan <krellan@google.com>
Change-Id: I164f0d67f0f350b9007db782ce33a17170ccd418
---
 README.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

(limited to 'README.md')

diff --git a/README.md b/README.md
index 715edc39a2..8e6a39be96 100644
--- a/README.md
+++ b/README.md
@@ -48,7 +48,8 @@ ninja -C builddir
 ### Generate test coverage report:
 ```ascii
 meson builddir -Db_coverage=true -Dtests=enabled
-ninja coverage -C builddir test
+ninja -C builddir test
+ninja -C builddir coverage
 ```
 When BMCWeb starts running, it reads persistent configuration data
 (such as UUID and session data) from a local file.  If this is not
-- 
cgit v1.2.3