Bug 199478 - tools/regression/sockets/unix_cmsg fails on 9.3-STABLE/10.1-STABLE/11-CURRENT (but only on amd64..?)
Summary: tools/regression/sockets/unix_cmsg fails on 9.3-STABLE/10.1-STABLE/11-CURRENT...
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: tests (show other bugs)
Version: 10.1-STABLE
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-testing mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-16 05:43 UTC by Enji Cooper
Modified: 2017-11-05 21:05 UTC (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Enji Cooper freebsd_committer 2015-04-16 05:43:34 UTC
"no data" seems to be the sticking point with this testcase failing.

AUDIT and MAC are disabled in the kernel and along with some drivers.

$ uname -a
FreeBSD fuji-stable-10.local 10.1-STABLE FreeBSD 10.1-STABLE #1 r277558+227bb2b(stable/10): Thu Jan 22 23:35:11 PST 2015     ngie@fuji-stable-10.local:/usr/obj/usr/src/sys/FUJI  amd64
$ cd tools/regression/sockets/unix_cmsg
$ prove -rv .
./unix_cmsg.t .. 
1..47
ok 1 - STREAM Sending, receiving cmsgcred 
not ok 2 - STREAM Sending, receiving cmsgcred (no data)
# SERVER: msghdr.msg_controllen 0 < 12
ok 3 - STREAM Sending, receiving cmsgcred (no array)
not ok 4 - STREAM Sending, receiving cmsgcred (no data, array)
# SERVER: msghdr.msg_controllen 0 < 12
ok 5 - STREAM Sending cmsgcred, receiving sockcred 
not ok 6 - STREAM Sending cmsgcred, receiving sockcred (no data)
# SERVER: msghdr.msg_controllen 0 < 12
ok 7 - STREAM Sending cmsgcred, receiving sockcred (no array)
not ok 8 - STREAM Sending cmsgcred, receiving sockcred (no data, array)
# SERVER: msghdr.msg_controllen 0 < 12
ok 9 - STREAM Sending, receiving timeval 
not ok 10 - STREAM Sending, receiving timeval (no data)
# SERVER: msghdr.msg_controllen 0 < 12
ok 11 - STREAM Sending, receiving timeval (no array)
not ok 12 - STREAM Sending, receiving timeval (no data, array)
# SERVER: msghdr.msg_controllen 0 < 12
ok 13 - STREAM Sending, receiving bintime 
not ok 14 - STREAM Sending, receiving bintime (no data)
# SERVER: msghdr.msg_controllen 0 < 12
ok 15 - STREAM Sending, receiving bintime (no array)
not ok 16 - STREAM Sending, receiving bintime (no data, array)
# SERVER: msghdr.msg_controllen 0 < 12
not ok 17 - STREAM Check cmsghdr.cmsg_len 
# CLIENT: sent message with cmsghdr.cmsg_len 12 < 16
# SERVER: client exit status is 1
not ok 18 - STREAM Check cmsghdr.cmsg_len (no data)
# CLIENT: sent message with cmsghdr.cmsg_len 12 < 16
# SERVER: client exit status is 1
not ok 19 - STREAM Check cmsghdr.cmsg_len (no array)
# CLIENT: sent message with cmsghdr.cmsg_len 12 < 16
# SERVER: client exit status is 1
not ok 20 - STREAM Check cmsghdr.cmsg_len (no data, array)
# CLIENT: sent message with cmsghdr.cmsg_len 12 < 16
# SERVER: client exit status is 1
ok 21 - STREAM Receiving sockcred (listening socket) 
ok 22 - STREAM Receiving sockcred (listening socket) (no data)
ok 23 - STREAM Receiving sockcred (accepted socket) 
ok 24 - STREAM Receiving sockcred (accepted socket) (no data)
ok 25 - STREAM Check LOCAL_PEERCRED socket option
ok 26 - DGRAM Sending, receiving cmsgcred 
not ok 27 - DGRAM Sending, receiving cmsgcred (no data)
# SERVER: msghdr.msg_flags has MSG_TRUNC
ok 28 - DGRAM Sending, receiving cmsgcred (no array)
not ok 29 - DGRAM Sending, receiving cmsgcred (no data, array)
# SERVER: msghdr.msg_flags has MSG_TRUNC
ok 30 - DGRAM Sending cmsgcred, receiving sockcred 
not ok 31 - DGRAM Sending cmsgcred, receiving sockcred (no data)
# SERVER: msghdr.msg_flags has MSG_TRUNC
ok 32 - DGRAM Sending cmsgcred, receiving sockcred (no array)
not ok 33 - DGRAM Sending cmsgcred, receiving sockcred (no data, array)
# SERVER: msghdr.msg_flags has MSG_TRUNC
ok 34 - DGRAM Sending, receiving timeval 
not ok 35 - DGRAM Sending, receiving timeval (no data)
# SERVER: msghdr.msg_flags has MSG_TRUNC
ok 36 - DGRAM Sending, receiving timeval (no array)
not ok 37 - DGRAM Sending, receiving timeval (no data, array)
# SERVER: msghdr.msg_flags has MSG_TRUNC
ok 38 - DGRAM Sending, receiving bintime 
not ok 39 - DGRAM Sending, receiving bintime (no data)
# SERVER: msghdr.msg_flags has MSG_TRUNC
ok 40 - DGRAM Sending, receiving bintime (no array)
not ok 41 - DGRAM Sending, receiving bintime (no data, array)
# SERVER: msghdr.msg_flags has MSG_TRUNC
not ok 42 - DGRAM Check cmsghdr.cmsg_len 
# CLIENT: sent message with cmsghdr.cmsg_len 12 < 16
# SERVER: client exit status is 1
not ok 43 - DGRAM Check cmsghdr.cmsg_len (no data)
# CLIENT: sent message with cmsghdr.cmsg_len 12 < 16
# SERVER: client exit status is 1
not ok 44 - DGRAM Check cmsghdr.cmsg_len (no array)
# CLIENT: sent message with cmsghdr.cmsg_len 12 < 16
# SERVER: client exit status is 1
not ok 45 - DGRAM Check cmsghdr.cmsg_len (no data, array)
# CLIENT: sent message with cmsghdr.cmsg_len 12 < 16
# SERVER: client exit status is 1
ok 46 - DGRAM Receiving sockcred 
not ok 47 - DGRAM Receiving sockcred (no data)
# SERVER: msghdr.msg_flags has MSG_TRUNC
Failed 25/47 subtests 

Test Summary Report
-------------------
./unix_cmsg.t (Wstat: 0 Tests: 47 Failed: 25)
  Failed tests:  2, 4, 6, 8, 10, 12, 14, 16-20, 27, 29, 31
                33, 35, 37, 39, 41-45, 47
Files=1, Tests=47,  0 wallclock secs ( 0.05 usr  0.01 sys +  0.06 cusr  0.20 csys =  0.32 CPU)
Result: FAIL
Comment 1 commit-hook freebsd_committer 2015-04-16 06:06:58 UTC
A commit references this bug:

Author: ngie
Date: Thu Apr 16 06:06:46 UTC 2015
New revision: 281588
URL: https://svnweb.freebsd.org/changeset/base/281588

Log:
  Update comments

  Don't install/test unix_cmsg because it's broken [1]

  PR: 199478

Changes:
  user/ngie/more-tests/tests/sys/socket/Makefile
Comment 2 Enji Cooper freebsd_committer 2015-04-16 09:49:20 UTC
Works fine on my r275110 (5 month old) i386 build. I suspect it's a test issue with amd64 vs i386...