Run_std

Question

Hi,
Is there a way to continue what's left in run_std after it's interrupted?
I recently compiled 4.3.29. The test is taking more than 1 day on my system and I've re-run it at least 4 times, because of various connection issues of the remote shell client.
Thanks

Answer 1

Hi, Carol,
Could you deciper for me why some of the tests
failed?
And, how do I repeat a specific test (say, -queueext
test097, which might be due to "ulimit -n") that
failed in "run_std"?
Thanks.
Hi,
I'll respond in line, below. I don't see anything scary here.
- Carol
===========================
Here are what came out of my nohup.out (Solaris
9/SPARC):
Test suite run started at: 12:29 08/08/2006
Sleepycat Software: Berkeley DB 4.3.29: (September
6, 2005)
Running environment tests
Running queueext tests
Running recno tests
Running rbtree tests
Running frecno tests
Running rrecno tests
UNEXPECTED OUTPUT: FAIL: run_subsystem: sdbtest
sdbtest002: illegal use of | or |& in commandThis is not your problem -- it's a test error that pops up on certain platforms that we have since corrected.
UNEXPECTED OUTPUT: FAIL:15:58:03 (00:00:00) r: sdb:
couldn't open "./TESTDIR/t4": no such file or
directoryCould you give me a little more context for this one? If you look in the ALL.OUT file, you'll be able to see what test it was running at the time of the failure.
UNEXPECTED OUTPUT: Secondary index join test.
UNEXPECTED OUTPUT: sijoin {[ list btree btree btree
]} 1000
UNEXPECTED OUTPUT: Secondary index join test.
UNEXPECTED OUTPUT: sijoin {[ list recno hash btree
]} 1000
UNEXPECTED OUTPUT: WARNING: log record type
__db_pg_new: not tested
UNEXPECTED OUTPUT: WARNING: log record type
__db_pg_prepare: not testedNone of the above six lines are significant.
UNEXPECTED OUTPUT: FAIL:test044 hash: child killed:
hangupThis looks like something related to your particular remote access situation. You can run test044 standalone if you'd like to make sure this doesn't repeat:
% test044 hash
will do the job.
UNEXPECTED OUTPUT: FAIL:17:41:46 (00:01:03)
run_method: -queueext test097: db put:too many open
filesYes, this is a resource shortage. If you raise the number of allowed open files using ulimit it should go away.
Regression Tests Failed
Check UNEXPECTED OUTPUT lines.
Review ALL.OUT.x for details.
Test suite run completed at: 23:14 08/09/2006