[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: HP-UX 11.00, 11i test failures with 1.0.2

From: Albert Chin <subversion-dev_at_mlists.thewrittenword.com>
Date: 2004-05-04 04:39:12 CEST

On Mon, May 03, 2004 at 09:35:27PM -0500, Ben Collins-Sussman wrote:
> Albert Chin wrote:
>
> > PASS: fs-test 1: svn_fs_create_berkeley
> > svn: Berkeley DB error while opening environment for filesystem
> > test-repo-open-berkeley:
> > Not enough space
> > FAIL: fs-test 2: open an existing Berkeley DB filesystem
> > PASS: fs-test 3: begin a txn, check its name, then close it
> >
> >Where do I start looking to find the source of the error?
>
> I would start by looking at the error message itself: "not enough
> space". Are you running 'make check' on a read-only filesystem? Or on
> a filesystem that's full?

'make check' is run on the file system where the build was done. So,
it's not read-only. BTW, strerror(ENOMEM) == 'Not enough space'. I
looked at the Berkeley DB documentation and found this:
  http://www.sleepycat.com/docs/ref/build_unix/hpux.html

  ...

  4. An ENOMEM error is returned from DB_ENV->open or DB_ENV->remove.

     Due to the constraints of the PA-RISC memory architecture, HP-UX does
     not allow a process to map a file into its address space multiple
     times. For this reason, each Berkeley DB environment may be opened
     only once by a process on HP-UX; that is, calls to DB_ENV->open will
     fail if the specified Berkeley DB environment has been opened and not
     subsequently closed.

Does this look like the culprit?

-- 
albert chin (china@thewrittenword.com)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 4 03:39:25 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.