aboutsummaryrefslogtreecommitdiff
path: root/net/unix/scm.c
diff options
context:
space:
mode:
authorDaniel Latypov <[email protected]>2020-09-30 11:31:51 -0700
committerShuah Khan <[email protected]>2020-10-09 14:04:09 -0600
commit1abdd39f14b25dd2d69096b624a4f86f158a9feb (patch)
treebd924bc6b2064dd28126c25e1142876a9e8301da /net/unix/scm.c
parent82206a0c06ccbd4a80cd623b9d52fcda130d6c7d (diff)
kunit: tool: fix display of make errors
CalledProcessError stores the output of the failed process as `bytes`, not a `str`. So when we log it on build error, the make output is all crammed into one line with "\n" instead of actually printing new lines. After this change, we get readable output with new lines, e.g. > CC lib/kunit/kunit-example-test.o > In file included from ../lib/kunit/test.c:9: > ../include/kunit/test.h:22:1: error: unknown type name ‘invalid_type_that_causes_compile’ > 22 | invalid_type_that_causes_compile errors; > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > make[3]: *** [../scripts/Makefile.build:283: lib/kunit/test.o] Error 1 Secondly, trying to concat exceptions to strings will fail with > TypeError: can only concatenate str (not "OSError") to str so fix this with an explicit cast to str. Signed-off-by: Daniel Latypov <[email protected]> Reviewed-by: Brendan Higgins <[email protected]> Tested-by: Brendan Higgins <[email protected]> Signed-off-by: Shuah Khan <[email protected]>
Diffstat (limited to 'net/unix/scm.c')
0 files changed, 0 insertions, 0 deletions