Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (athena.apache.org: domain of knut.hatlen@oracle.com
 designates 141.146.126.69 as permitted sender)
From: Knut Anders Hatlen <knut.hatlen@oracle.com>
To: <derby-dev@db.apache.org>
Subject: Re: Jacoco exception
References: <51D786F1.3020502@gmail.com> <87ip0nlaq4.fsf@oracle.com>
	<CAEJ0U-6um-GinNNd48kvuhZoCVkUADGHAaJEym0_gHnvWtdKDw@mail.gmail.com>
Mail-Copies-To: never
Mail-Followup-To: <derby-dev@db.apache.org>
Date: Mon, 08 Jul 2013 14:38:20 +0200
In-Reply-To: 
 <CAEJ0U-6um-GinNNd48kvuhZoCVkUADGHAaJEym0_gHnvWtdKDw@mail.gmail.com>
	(Kristian Waagan's message of "Sat, 6 Jul 2013 22:12:23 +0200")
Message-ID: <87zjtxb51f.fsf@oracle.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain

Kristian Waagan <kristwaa@apache.org> writes:

> Hi,
>
> This is a bug in ASM, see
> http://forge.ow2.org/tracker/?func=detail&atid=100023&aid=316416&group_id=23.
>
> We'll have to wait until JaCoCo picks up ASM with the fix, or exclude
> the Derby version containing the code triggering the bug. But as Knut
> said, the coverage results look reasonable.

Thanks for that pointer, Kristian.

It looks like the bug was closed as invalid because the class that
triggered the error was not valid, probably produced by a buggy
compiler. So I'm not sure if the proposed patch ever went into ASM.

I've logged https://issues.apache.org/jira/browse/DERBY-6288 to exclude
10.0.2.1 when we're running with JaCoCo.

I'm also seeing four network tests in derbyall fail with "connection
refused" when I'm running JaCoCo. They're also failing when running
EMMA. I'm not planning to investigate this issue now, since I assume it
will go away once these tests have been migrated to JUnit. (I think
those four tests are the only remaining network tests in derbyall.)

-- 
Knut Anders