[Intel-gfx] [PATCH i-g-t 2/4] core: Put the requirement failure messages together

Damien Lespiau damien.lespiau at intel.com
Wed Jul 9 12:45:19 CEST 2014


The errno message was a bit in the middle here, it makes more sense to
group the messages about why the test requirement wasn't met together.

Signed-off-by: Damien Lespiau <damien.lespiau at intel.com>
---
 lib/igt_core.c | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/lib/igt_core.c b/lib/igt_core.c
index 364cdd0..4dbcb1a 100644
--- a/lib/igt_core.c
+++ b/lib/igt_core.c
@@ -588,16 +588,16 @@ void __igt_skip_check(const char *file, const int line,
 		va_end(args);
 
 		igt_skip("Test requirement not met in function %s, file %s:%i:\n"
-			 "Last errno: %i, %s\n"
-			 "Test requirement: (%s)\n%s",
-			 func, file, line, err, strerror(err), check, buf);
+			 "Test requirement: (%s)\n%s"
+			 "Last errno: %i, %s\n",
+			 func, file, line, check, buf, err, strerror(err));
 
 		free(buf);
 	} else {
 		igt_skip("Test requirement not met in function %s, file %s:%i:\n"
-			 "Last errno: %i, %s\n"
-			 "Test requirement: (%s)\n",
-			 func, file, line, err, strerror(err), check);
+			 "Test requirement: (%s)\n"
+			 "Last errno: %i, %s\n",
+			 func, file, line, check, err, strerror(err));
 	}
 }
 
-- 
1.8.3.1




More information about the Intel-gfx mailing list