Has anyone had a problem running the OS test on out of the box TurboLinux 65? It seems to be killing the tests. Here is a screen capture of the screen output, journal, and report of the run. I have run the test twice & both times it didn't finish. Is there anything I can do to get the test to complete? Chris -- This is definitely going to impact the database work you are doing. The Turbo report that Arnold sent you has the same problem. Executing testsets tcc: journal file is /home/tet/test_sets/results/0002e/journal 10:57:45 Execute /tset/LSB.os/aio/aio_cancel/T.aio_cancel 10:58:37 Execute /tset/LSB.os/aio/aio_error/T.aio_error 10:58:52 Execute /tset/LSB.os/aio/aio_fsync/T.aio_fsync 10:58:53 Execute /tset/LSB.os/aio/aio_read/T.aio_read 10:59:23 Execute /tset/LSB.os/aio/aio_read_X/T.aio_read_X 10:59:24 Execute /tset/LSB.os/aio/aio_return/T.aio_return 10:59:45 Execute /tset/LSB.os/aio/aio_suspend/T.aio_suspend 11:04:02 Execute /tset/LSB.os/aio/aio_write/T.aio_write 11:05:03 Execute /tset/LSB.os/aio/aio_write_X/T.aio_write_X 11:05:04 Execute /tset/LSB.os/aio/lio_listio/T.lio_listio run_testsets.sh: line 14: 2983 Killed tcc -p -e -s $HOME/scen.exec $* Results: Total tests: 104 PASS = 73 FAIL = 31 Pass Breakdown: Number of successes: 28 Number of warnings: 0 Number unsupported: 26 Number not in use: 1 Number of untested: 18 Number of FIP: 0 Unapproved assertions: 0 Number not implemented: 0 Failure Breakdown: Number of failures: 29 Number unresolved: 2 Number uninitiated: 0 Number unreported: 0 A formal report has been saved in /home/tet/test_sets/results/report warning: journal file does not end with correct control sequence vrpt.page: completed page 25 (See attached file: turbo65osjournal) Any help is greatly appreciate, Lisa Sarabia SW Engineer Linux Technology Center (512) 838-9466 T/L 678-9466
Attachment:
turbo65osjournal
Description: Binary data