On Sat, Sep 06, 2008 at 10:56:04AM +0200, Florian Weimer wrote:
> * Steve Langasek:
> > Well, obviously it's not any of these errors since this is their own test
> > suite... but done anyway, to see what kind of output we get:
> > FILE *errfile;
> > errfile = fopen("/home/vorlon/debuggin
* Steve Langasek:
> Well, obviously it's not any of these errors since this is their own test
> suite... but done anyway, to see what kind of output we get:
>
> FILE *errfile;
>
> errfile = fopen("/home/vorlon/debugging-db.log", "w");
> i = db_env_create(&env, 0);
> i = env->set_en
On Fri, Sep 05, 2008 at 08:42:05AM +, Clint Adams wrote:
> On Wed, Sep 03, 2008 at 10:13:36PM -0700, Steve Langasek wrote:
> > But figuring out where this EINVAL originates seems to be non-trivial.
> Suggestion from Oracle:
> | Please configure an error stream, with DB_ENV->set_errfile. That
On Wed, Sep 03, 2008 at 10:13:36PM -0700, Steve Langasek wrote:
> But figuring out where this EINVAL originates seems to be non-trivial.
Suggestion from Oracle:
| Please configure an error stream, with DB_ENV->set_errfile. That should
| indicate the cause of the error. If the named database file
On Wed, Sep 03, 2008 at 10:13:36PM -0700, Steve Langasek wrote:
> This gives the EINVAL from the tcl test, and appears to be otherwise
> correct.
>
> But figuring out where this EINVAL originates seems to be non-trivial.
"forwarded" to
http://forums.oracle.com/forums/thread.jspa?threadID=702100&t
On Wed, Sep 03, 2008 at 07:52:30PM +, Clint Adams wrote:
> On Tue, Sep 02, 2008 at 01:33:54AM -0700, Steve Langasek wrote:
> > echo "source ../test/test.tcl; run_std env007" | tclsh8.5
> > How do these tcl commands map to C, for better debugging?
> Without looking into the tcl bindings, I w
On Tue, Sep 02, 2008 at 01:33:54AM -0700, Steve Langasek wrote:
> echo "source ../test/test.tcl; run_std env007" | tclsh8.5
>
> How do these tcl commands map to C, for better debugging?
Without looking into the tcl bindings, I would guess that
berkdb_env -create -home ./TESTDIR -txn -encryptae
Investigating on agnesi, I see that this is the failing bit of the test:
berkdb_open -create -btree -mode 0644 -env env1 -encrypt a.db
whereas this command immediately before it works fine:
berkdb_open -create -btree -mode 0644 -env env0 -auto_commit a.db
so it looks like this is a proble
On Tue, Nov 06, 2007 at 11:15:07PM +, brian m. carlson wrote:
> Since this is an RC bug, I'd like to see it fixed. If the maintainer and
> submitter feel that accepting testsuite errors is okay (which is the
> current situation, according to b.d.o), then please close this bug.
I think that
On Tue, Aug 14, 2007 at 10:07:01AM +0300, Riku Voipio wrote:
On Mon, Aug 13, 2007 at 06:49:06PM -0400, Clint Adams wrote:
! grep ^FAIL obj/ALL.OUT
FAIL: run_subsystem: env env007: db open:invalid argument
make: *** [build] Error 1
This testsuite failure has happened *all* db, db4.5, db4.4 and
On Mon, Aug 13, 2007 at 06:49:06PM -0400, Clint Adams wrote:
> http://buildd.debian.org/fetch.cgi?pkg=db;ver=4.6.18-4;arch=arm;stamp=1187033603
> Modified test suite run started at: 09:02 08/13/07
> Berkeley DB 4.6.18: (July 17, 2007)
> Running environment tests (09:02:08)
> Running archive tests
Package: db
Version: 4.6.18-1
Severity: serious
http://buildd.debian.org/fetch.cgi?pkg=db;ver=4.6.18-4;arch=arm;stamp=1187033603
Modified test suite run started at: 09:02 08/13/07
Berkeley DB 4.6.18: (July 17, 2007)
Running environment tests (09:02:08)
Running archive tests (09:06:40)
Running bac
12 matches
Mail list logo
