Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of brian.havard@gmail.com
 designates 209.85.218.216 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject
         :x-enigmail-version:content-type:content-transfer-encoding;
        b=NCyf45yfMPVexMU94FC0oi6c5C7qkWhCTpvxYUCddBzwpZmUI/yXLjkpfjQUQvXyGX
         gQ9YKdYr6n+qWP22oFDB3lYyPvYr+PKfwNk+Ju+9LtpCnq6Rz+uNSEL/8NuHMThuQe9Y
         ak4QhHxsc1F7HJwGdgaUEAVEAb+qTrhAoPzu8=
Message-ID: <4BB903D1.5030607@gmail.com>
Date: Sun, 04 Apr 2010 22:25:37 +0100
From: Brian Havard <brian.havard@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100317)
MIME-Version: 1.0
To: dev@apr.apache.org
Subject: Test suit oddities
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

I've been working my way through the test suit on OS/2 and have hit a
couple of oddities where I think the test needs to be changed.

- testdso: test_unload_library() closes the library with
apr_dso_unload() and then expects apr_dso_sym() to return
APR_ESYMNOTFOUND. WTF? That's like expecting read() to return EOF on a
closed handle. Surely something like EBADF would be more appropriate. I
had a look at the unix implementation and I can see why it passes, it
returns APR_ESYMNOTFOUND for every single failure! I'd suggest just
testing for != APR_SUCCESS.

- testcond: nested_wait() creates a thread that exits while owning a
mutex and then tries to lock that mutex, expecting the result to be
EBUSY. On OS/2, when a thread exits while owning a mutex, that mutex has
an indeterminate state and any attempt to lock it returns
ERROR_SEM_OWNER_DIED. I don't see any problem with this behaviour so
would anyone object to me changing the test so that the owning thread
stays alive long enough for the primary thread to do its
apr_thread_mutex_trylock()?