Here are the tests that failed. Note that n0 is a generated name, name255 is a 255 character string, and path 1023 is a 1023 long path
/opt/qa/tools/posix-testsuite/tests/link/02.t (Wstat: 0 Tests: 10 Failed: 2) Failed tests: 4, 6 expect 0 link ${n0} ${name255} #4 expect 0 unlink ${n0} #5 <- this passed expect 0 unlink ${name255} #6 /opt/qa/tools/posix-testsuite/tests/link/03.t (Wstat: 0 Tests: 16 Failed: 2) Failed tests: 8-9 expect 0 link ${n0} ${path1023} #8 expect 0 unlink ${path1023} #9 I gotta go for the day, I'll try to repro outside the script tomorrow. -b On Tue, Jun 17, 2014 at 11:09 AM, Benjamin Turner <bennytu...@gmail.com> wrote: > I ran through fs sanity on the beta 2 bits: > > ================ final pass/fail report ================= > Test Date: Mon Jun 16 23:41:51 EDT 2014 > Total : [44] > Passed: [42] > Failed: [2] > Abort : [0] > Crash : [0] > --------------------------------------------------------- > [ PASS ] FS Sanity Setup > [ PASS ] Running tests. > [ PASS ] FS SANITY TEST - arequal > [ PASS ] FS SANITY LOG SCAN - arequal > [ PASS ] FS SANITY TEST - bonnie > [ PASS ] FS SANITY LOG SCAN - bonnie > [ PASS ] FS SANITY TEST - glusterfs_build > [ PASS ] FS SANITY LOG SCAN - glusterfs_build > [ PASS ] FS SANITY TEST - compile_kernel > [ PASS ] FS SANITY LOG SCAN - compile_kernel > [ PASS ] FS SANITY TEST - dbench > [ PASS ] FS SANITY LOG SCAN - dbench > [ PASS ] FS SANITY TEST - dd > [ PASS ] FS SANITY LOG SCAN - dd > [ PASS ] FS SANITY TEST - ffsb > [ PASS ] FS SANITY LOG SCAN - ffsb > [ PASS ] FS SANITY TEST - fileop > [ PASS ] FS SANITY LOG SCAN - fileop > [ PASS ] FS SANITY TEST - fsx > [ PASS ] FS SANITY LOG SCAN - fsx > [ PASS ] FS SANITY TEST - fs_mark > [ PASS ] FS SANITY LOG SCAN - fs_mark > [ PASS ] FS SANITY TEST - iozone > [ PASS ] FS SANITY LOG SCAN - iozone > [ PASS ] FS SANITY TEST - locks > [ PASS ] FS SANITY LOG SCAN - locks > [ PASS ] FS SANITY TEST - ltp > [ PASS ] FS SANITY LOG SCAN - ltp > [ PASS ] FS SANITY TEST - multiple_files > [ PASS ] FS SANITY LOG SCAN - multiple_files > [ PASS ] FS SANITY LOG SCAN - posix_compliance > [ PASS ] FS SANITY TEST - postmark > [ PASS ] FS SANITY LOG SCAN - postmark > [ PASS ] FS SANITY TEST - read_large > [ PASS ] FS SANITY LOG SCAN - read_large > [ PASS ] FS SANITY TEST - rpc > [ PASS ] FS SANITY LOG SCAN - rpc > [ PASS ] FS SANITY TEST - syscallbench > [ PASS ] FS SANITY LOG SCAN - syscallbench > [ PASS ] FS SANITY TEST - tiobench > [ PASS ] FS SANITY LOG SCAN - tiobench > [ PASS ] FS Sanity Cleanup > > [ FAIL ] FS SANITY TEST - posix_compliance > [ FAIL ] > /rhs-tests/beaker/rhs/auto-tests/components/sanity/fs-sanity-tests-v2 > > > The posix_compliance failures are: > > /opt/qa/tools/posix-testsuite/tests/link/02.t ...... > > Failed 2/10 subtests > > /opt/qa/tools/posix-testsuite/tests/link/03.t ...... > Failed 2/16 subtests > > I am looking into the failures now as well as running on NFS mounts, I will > open a BZ if they are valid. > > -b > > > >
_______________________________________________ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel