Follow 0/-E convention for module load errors

Because errors during module load are so rare it went unnoticed that
it was possible that a positive errno was returned.  This would result
in the module being loaded, nothing being initialized, and a system
panic shortly thereafter.  This is what was causing the hard failures
in the automated testing.

Signed-off-by: Brian Behlendorf <[email protected]>

1 files changed, 0 insertions, 4 deletions

diff --git a/TEST b/TEST
index 05818faf7..eba35a37d 100644
--- a/TEST
+++ b/TEST
@@ -71,14 +71,10 @@ case "$BB_NAME" in
 Amazon*)
     ;;
 CentOS*)
-    # Fails vnode:vn_rdwr, CentOS 6.
-    TEST_SPLAT_SKIP="yes"
     # Sporadic segmentation faults
     TEST_ZTEST_SKIP="yes"
     # Sporadic VERIFY(!zilog_is_dirty(zilog)) failed
     TEST_ZILTEST_SKIP="yes"
-    # Hangs loading modules
-    TEST_ZCONFIG_SKIP="yes"
     ;;
 Debian*)
     ;;