You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by Flavio Junqueira <fp...@apache.org> on 2015/11/01 16:24:58 UTC
Test failure
This test seems to be failing frequently in trunk, has anyone had a look at this:
org.apache.zookeeper.test.ClientPortBindTest.testBindByAddress <https://builds.apache.org/view/All/job/ZooKeeper-trunk/2803/testReport/org.apache.zookeeper.test/ClientPortBindTest/testBindByAddress/>
Error Details <> Error Details
Forked Java VM exited abnormally. Please note the time in the report does not reflect the time until the VM exit.
Stack Trace <> Stack Trace
-Flavio
Re: Test failure
Posted by Chris Nauroth <cn...@hortonworks.com>.
Michi, thanks for updating those Jenkins jobs.
I think it's valuable to keep the 3.4 Java 6 job only if we are committing
to maintaining compatibility with Java 6 within that branch. (I would
think that we do need to maintain compatibility with Java 6, since it's
supposed to be a maintenance line.) That job can let us know if we
accidentally commit Java 7-specific API calls into the branch.
--Chris Nauroth
On 11/2/15, 7:15 AM, "Flavio Junqueira" <fp...@apache.org> wrote:
>Yep, sounds good, thanks Michi & Chris.
>
>We have a queue for the 3.4 branch running Java 6. Do folks still care
>about running it on Java 6? Should we get rid of that queue?
>
>-Flavio
>
>> On 02 Nov 2015, at 07:02, Michi Mutsuzaki <mu...@gmail.com> wrote:
>>
>> I updated these jobs to use Oracle JDK 1.7.0_72. ClientPortBindTest
>> seems to be passing now.
>>
>> https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper-trunk/
>>
>>https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper_branch35_
>>jdk7/
>>
>>https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper_branch34_
>>jdk7/
>>
>>https://builds.apache.org/view/S-Z/view/ZooKeeper/job/PreCommit-ZOOKEEPER
>>-Build/
>>
>>
>> On Sun, Nov 1, 2015 at 6:09 PM, Michi Mutsuzaki <mu...@gmail.com>
>>wrote:
>>> Let me try running the build with the latest 1.7 jdk and see if it
>>>helps.
>>>
>>> On Sun, Nov 1, 2015 at 5:46 PM, Michi Mutsuzaki <mu...@gmail.com>
>>>wrote:
>>>> Chris, which log file are you looking at? I looked at
>>>>
>>>>https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper-trunk/2
>>>>806/consoleFull
>>>> and it seems to be using Oracle JDK 1.7.0-64.
>>>>
>>>> [junit] 2015-11-01 11:04:05,246 [myid:] - INFO
>>>> [main:Environment@109] - Server environment:java.version=1.7.0
>>>> [junit] 2015-11-01 11:04:05,249 [myid:] - INFO
>>>> [main:Environment@109] - Server environment:java.vendor=Oracle
>>>> Corporation
>>>> [junit] 2015-11-01 11:04:05,249 [myid:] - INFO
>>>> [main:Environment@109] - Server
>>>> environment:java.home=/home/jenkins/tools/java/jdk1.7.0-64/jre
>>>>
>>>> On Sun, Nov 1, 2015 at 1:49 PM, Chris Nauroth
>>>><cn...@hortonworks.com> wrote:
>>>>>
>>>>> Digging into the console log, I found evidence of a memory
>>>>>corruption error at the JVM level.
>>>>>
>>>>> [exec] [junit] Running
>>>>>org.apache.zookeeper.test.ClientPortBindTest in thread 2
>>>>> [exec] [junit] 2015-10-31 22:43:13,546 [myid:] - INFO
>>>>>[main:JUnit4ZKTestRunner@47] - No test.method specified. using
>>>>>default methods.
>>>>> [exec] [junit] 2015-10-31 22:43:13,558 [myid:] - INFO
>>>>>[main:ZKTestCase$1@55] - STARTING testBindByAddress
>>>>> [exec] [junit] 2015-10-31 22:43:13,559 [myid:] - INFO
>>>>>[main:JUnit4ZKTestRunner$LoggedInvokeMethod@77] - RUNNING TEST METHOD
>>>>>testBindByAddress
>>>>> [exec] [junit] *** Error in
>>>>>`/home/jenkins/tools/java/jdk1.7.0-64/jre/bin/java': malloc(): memory
>>>>>corruption: 0x00007ffc2c31e220 ***
>>>>> [exec] [junit] Test
>>>>>org.apache.zookeeper.test.ClientPortBindTest FAILED (crashed)
>>>>> [exec] [junit] Running
>>>>>org.apache.zookeeper.test.ClientPortBindTest in thread 2
>>>>> [exec] [junit] Tests run: 1, Failures: 0, Errors: 1,
>>>>>Skipped: 0, Time elapsed: 0 sec, Thread: 2, Class:
>>>>>org.apache.zookeeper.test.ClientPortBindTest
>>>>>
>>>>> That's odd. ClientPortBindTest is purely a Java test. We aren't
>>>>>doing JNI or anything.
>>>>>
>>>>> The test calls NetworkInterface.getNetworkInterfaces(). Looking
>>>>>through JDK bug reports, I see that there have been memory management
>>>>>bugs in this method.
>>>>>
>>>>> https://bugs.openjdk.java.net/browse/JDK-7075227
>>>>>
>>>>> https://bugs.openjdk.java.net/browse/JDK-8013140
>>>>>
>>>>> https://bugs.openjdk.java.net/browse/JDK-8033146
>>>>>
>>>>> The console log also shows that we're running a fairly old version
>>>>>of Java 7.
>>>>>
>>>>> java version "1.7.0_25"
>>>>> Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
>>>>> Java HotSpot(TM) Server VM (build 23.25-b01, mixed mode)
>>>>>
>>>>> I cannot repro this in any of my own environments, including a Java
>>>>>1.7.0_67 environment and a Java 1.8.0_45 environment.
>>>>>
>>>>> I think it's likely that we're looking at an old Java bug, not a
>>>>>problem in the ZooKeeper codebase. If others agree, then I can file
>>>>>an INFRA JIRA to ask them for an upgrade to the latest Java 7
>>>>>revision on our Jenkins hosts.
>>>>>
>>>>> --Chris Nauroth
>>>>>
>>>>> From: Flavio Junqueira <fp...@apache.org>
>>>>> Reply-To: Zookeeper <de...@zookeeper.apache.org>
>>>>> Date: Sunday, November 1, 2015 at 8:24 AM
>>>>> To: Zookeeper <de...@zookeeper.apache.org>
>>>>> Subject: Test failure
>>>>>
>>>>> This test seems to be failing frequently in trunk, has anyone had a
>>>>>look at this:
>>>>>
>>>>> org.apache.zookeeper.test.ClientPortBindTest.testBindByAddress
>>>>>
>>>>> Error Details
>>>>>
>>>>> Forked Java VM exited abnormally. Please note the time in the report
>>>>>does not reflect the time until the VM exit.
>>>>>
>>>>> Stack Trace
>>>>>
>>>>>
>>>>> -Flavio
>
>
Re: Test failure
Posted by Flavio Junqueira <fp...@apache.org>.
Yep, sounds good, thanks Michi & Chris.
We have a queue for the 3.4 branch running Java 6. Do folks still care about running it on Java 6? Should we get rid of that queue?
-Flavio
> On 02 Nov 2015, at 07:02, Michi Mutsuzaki <mu...@gmail.com> wrote:
>
> I updated these jobs to use Oracle JDK 1.7.0_72. ClientPortBindTest
> seems to be passing now.
>
> https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper-trunk/
> https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper_branch35_jdk7/
> https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper_branch34_jdk7/
> https://builds.apache.org/view/S-Z/view/ZooKeeper/job/PreCommit-ZOOKEEPER-Build/
>
>
> On Sun, Nov 1, 2015 at 6:09 PM, Michi Mutsuzaki <mu...@gmail.com> wrote:
>> Let me try running the build with the latest 1.7 jdk and see if it helps.
>>
>> On Sun, Nov 1, 2015 at 5:46 PM, Michi Mutsuzaki <mu...@gmail.com> wrote:
>>> Chris, which log file are you looking at? I looked at
>>> https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper-trunk/2806/consoleFull
>>> and it seems to be using Oracle JDK 1.7.0-64.
>>>
>>> [junit] 2015-11-01 11:04:05,246 [myid:] - INFO
>>> [main:Environment@109] - Server environment:java.version=1.7.0
>>> [junit] 2015-11-01 11:04:05,249 [myid:] - INFO
>>> [main:Environment@109] - Server environment:java.vendor=Oracle
>>> Corporation
>>> [junit] 2015-11-01 11:04:05,249 [myid:] - INFO
>>> [main:Environment@109] - Server
>>> environment:java.home=/home/jenkins/tools/java/jdk1.7.0-64/jre
>>>
>>> On Sun, Nov 1, 2015 at 1:49 PM, Chris Nauroth <cn...@hortonworks.com> wrote:
>>>>
>>>> Digging into the console log, I found evidence of a memory corruption error at the JVM level.
>>>>
>>>> [exec] [junit] Running org.apache.zookeeper.test.ClientPortBindTest in thread 2
>>>> [exec] [junit] 2015-10-31 22:43:13,546 [myid:] - INFO [main:JUnit4ZKTestRunner@47] - No test.method specified. using default methods.
>>>> [exec] [junit] 2015-10-31 22:43:13,558 [myid:] - INFO [main:ZKTestCase$1@55] - STARTING testBindByAddress
>>>> [exec] [junit] 2015-10-31 22:43:13,559 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@77] - RUNNING TEST METHOD testBindByAddress
>>>> [exec] [junit] *** Error in `/home/jenkins/tools/java/jdk1.7.0-64/jre/bin/java': malloc(): memory corruption: 0x00007ffc2c31e220 ***
>>>> [exec] [junit] Test org.apache.zookeeper.test.ClientPortBindTest FAILED (crashed)
>>>> [exec] [junit] Running org.apache.zookeeper.test.ClientPortBindTest in thread 2
>>>> [exec] [junit] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 sec, Thread: 2, Class: org.apache.zookeeper.test.ClientPortBindTest
>>>>
>>>> That's odd. ClientPortBindTest is purely a Java test. We aren't doing JNI or anything.
>>>>
>>>> The test calls NetworkInterface.getNetworkInterfaces(). Looking through JDK bug reports, I see that there have been memory management bugs in this method.
>>>>
>>>> https://bugs.openjdk.java.net/browse/JDK-7075227
>>>>
>>>> https://bugs.openjdk.java.net/browse/JDK-8013140
>>>>
>>>> https://bugs.openjdk.java.net/browse/JDK-8033146
>>>>
>>>> The console log also shows that we're running a fairly old version of Java 7.
>>>>
>>>> java version "1.7.0_25"
>>>> Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
>>>> Java HotSpot(TM) Server VM (build 23.25-b01, mixed mode)
>>>>
>>>> I cannot repro this in any of my own environments, including a Java 1.7.0_67 environment and a Java 1.8.0_45 environment.
>>>>
>>>> I think it's likely that we're looking at an old Java bug, not a problem in the ZooKeeper codebase. If others agree, then I can file an INFRA JIRA to ask them for an upgrade to the latest Java 7 revision on our Jenkins hosts.
>>>>
>>>> --Chris Nauroth
>>>>
>>>> From: Flavio Junqueira <fp...@apache.org>
>>>> Reply-To: Zookeeper <de...@zookeeper.apache.org>
>>>> Date: Sunday, November 1, 2015 at 8:24 AM
>>>> To: Zookeeper <de...@zookeeper.apache.org>
>>>> Subject: Test failure
>>>>
>>>> This test seems to be failing frequently in trunk, has anyone had a look at this:
>>>>
>>>> org.apache.zookeeper.test.ClientPortBindTest.testBindByAddress
>>>>
>>>> Error Details
>>>>
>>>> Forked Java VM exited abnormally. Please note the time in the report does not reflect the time until the VM exit.
>>>>
>>>> Stack Trace
>>>>
>>>>
>>>> -Flavio
Re: Test failure
Posted by Michi Mutsuzaki <mu...@gmail.com>.
I updated these jobs to use Oracle JDK 1.7.0_72. ClientPortBindTest
seems to be passing now.
https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper-trunk/
https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper_branch35_jdk7/
https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper_branch34_jdk7/
https://builds.apache.org/view/S-Z/view/ZooKeeper/job/PreCommit-ZOOKEEPER-Build/
On Sun, Nov 1, 2015 at 6:09 PM, Michi Mutsuzaki <mu...@gmail.com> wrote:
> Let me try running the build with the latest 1.7 jdk and see if it helps.
>
> On Sun, Nov 1, 2015 at 5:46 PM, Michi Mutsuzaki <mu...@gmail.com> wrote:
>> Chris, which log file are you looking at? I looked at
>> https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper-trunk/2806/consoleFull
>> and it seems to be using Oracle JDK 1.7.0-64.
>>
>> [junit] 2015-11-01 11:04:05,246 [myid:] - INFO
>> [main:Environment@109] - Server environment:java.version=1.7.0
>> [junit] 2015-11-01 11:04:05,249 [myid:] - INFO
>> [main:Environment@109] - Server environment:java.vendor=Oracle
>> Corporation
>> [junit] 2015-11-01 11:04:05,249 [myid:] - INFO
>> [main:Environment@109] - Server
>> environment:java.home=/home/jenkins/tools/java/jdk1.7.0-64/jre
>>
>> On Sun, Nov 1, 2015 at 1:49 PM, Chris Nauroth <cn...@hortonworks.com> wrote:
>>>
>>> Digging into the console log, I found evidence of a memory corruption error at the JVM level.
>>>
>>> [exec] [junit] Running org.apache.zookeeper.test.ClientPortBindTest in thread 2
>>> [exec] [junit] 2015-10-31 22:43:13,546 [myid:] - INFO [main:JUnit4ZKTestRunner@47] - No test.method specified. using default methods.
>>> [exec] [junit] 2015-10-31 22:43:13,558 [myid:] - INFO [main:ZKTestCase$1@55] - STARTING testBindByAddress
>>> [exec] [junit] 2015-10-31 22:43:13,559 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@77] - RUNNING TEST METHOD testBindByAddress
>>> [exec] [junit] *** Error in `/home/jenkins/tools/java/jdk1.7.0-64/jre/bin/java': malloc(): memory corruption: 0x00007ffc2c31e220 ***
>>> [exec] [junit] Test org.apache.zookeeper.test.ClientPortBindTest FAILED (crashed)
>>> [exec] [junit] Running org.apache.zookeeper.test.ClientPortBindTest in thread 2
>>> [exec] [junit] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 sec, Thread: 2, Class: org.apache.zookeeper.test.ClientPortBindTest
>>>
>>> That's odd. ClientPortBindTest is purely a Java test. We aren't doing JNI or anything.
>>>
>>> The test calls NetworkInterface.getNetworkInterfaces(). Looking through JDK bug reports, I see that there have been memory management bugs in this method.
>>>
>>> https://bugs.openjdk.java.net/browse/JDK-7075227
>>>
>>> https://bugs.openjdk.java.net/browse/JDK-8013140
>>>
>>> https://bugs.openjdk.java.net/browse/JDK-8033146
>>>
>>> The console log also shows that we're running a fairly old version of Java 7.
>>>
>>> java version "1.7.0_25"
>>> Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
>>> Java HotSpot(TM) Server VM (build 23.25-b01, mixed mode)
>>>
>>> I cannot repro this in any of my own environments, including a Java 1.7.0_67 environment and a Java 1.8.0_45 environment.
>>>
>>> I think it's likely that we're looking at an old Java bug, not a problem in the ZooKeeper codebase. If others agree, then I can file an INFRA JIRA to ask them for an upgrade to the latest Java 7 revision on our Jenkins hosts.
>>>
>>> --Chris Nauroth
>>>
>>> From: Flavio Junqueira <fp...@apache.org>
>>> Reply-To: Zookeeper <de...@zookeeper.apache.org>
>>> Date: Sunday, November 1, 2015 at 8:24 AM
>>> To: Zookeeper <de...@zookeeper.apache.org>
>>> Subject: Test failure
>>>
>>> This test seems to be failing frequently in trunk, has anyone had a look at this:
>>>
>>> org.apache.zookeeper.test.ClientPortBindTest.testBindByAddress
>>>
>>> Error Details
>>>
>>> Forked Java VM exited abnormally. Please note the time in the report does not reflect the time until the VM exit.
>>>
>>> Stack Trace
>>>
>>>
>>> -Flavio
Re: Test failure
Posted by Michi Mutsuzaki <mu...@gmail.com>.
Let me try running the build with the latest 1.7 jdk and see if it helps.
On Sun, Nov 1, 2015 at 5:46 PM, Michi Mutsuzaki <mu...@gmail.com> wrote:
> Chris, which log file are you looking at? I looked at
> https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper-trunk/2806/consoleFull
> and it seems to be using Oracle JDK 1.7.0-64.
>
> [junit] 2015-11-01 11:04:05,246 [myid:] - INFO
> [main:Environment@109] - Server environment:java.version=1.7.0
> [junit] 2015-11-01 11:04:05,249 [myid:] - INFO
> [main:Environment@109] - Server environment:java.vendor=Oracle
> Corporation
> [junit] 2015-11-01 11:04:05,249 [myid:] - INFO
> [main:Environment@109] - Server
> environment:java.home=/home/jenkins/tools/java/jdk1.7.0-64/jre
>
> On Sun, Nov 1, 2015 at 1:49 PM, Chris Nauroth <cn...@hortonworks.com> wrote:
>>
>> Digging into the console log, I found evidence of a memory corruption error at the JVM level.
>>
>> [exec] [junit] Running org.apache.zookeeper.test.ClientPortBindTest in thread 2
>> [exec] [junit] 2015-10-31 22:43:13,546 [myid:] - INFO [main:JUnit4ZKTestRunner@47] - No test.method specified. using default methods.
>> [exec] [junit] 2015-10-31 22:43:13,558 [myid:] - INFO [main:ZKTestCase$1@55] - STARTING testBindByAddress
>> [exec] [junit] 2015-10-31 22:43:13,559 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@77] - RUNNING TEST METHOD testBindByAddress
>> [exec] [junit] *** Error in `/home/jenkins/tools/java/jdk1.7.0-64/jre/bin/java': malloc(): memory corruption: 0x00007ffc2c31e220 ***
>> [exec] [junit] Test org.apache.zookeeper.test.ClientPortBindTest FAILED (crashed)
>> [exec] [junit] Running org.apache.zookeeper.test.ClientPortBindTest in thread 2
>> [exec] [junit] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 sec, Thread: 2, Class: org.apache.zookeeper.test.ClientPortBindTest
>>
>> That's odd. ClientPortBindTest is purely a Java test. We aren't doing JNI or anything.
>>
>> The test calls NetworkInterface.getNetworkInterfaces(). Looking through JDK bug reports, I see that there have been memory management bugs in this method.
>>
>> https://bugs.openjdk.java.net/browse/JDK-7075227
>>
>> https://bugs.openjdk.java.net/browse/JDK-8013140
>>
>> https://bugs.openjdk.java.net/browse/JDK-8033146
>>
>> The console log also shows that we're running a fairly old version of Java 7.
>>
>> java version "1.7.0_25"
>> Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
>> Java HotSpot(TM) Server VM (build 23.25-b01, mixed mode)
>>
>> I cannot repro this in any of my own environments, including a Java 1.7.0_67 environment and a Java 1.8.0_45 environment.
>>
>> I think it's likely that we're looking at an old Java bug, not a problem in the ZooKeeper codebase. If others agree, then I can file an INFRA JIRA to ask them for an upgrade to the latest Java 7 revision on our Jenkins hosts.
>>
>> --Chris Nauroth
>>
>> From: Flavio Junqueira <fp...@apache.org>
>> Reply-To: Zookeeper <de...@zookeeper.apache.org>
>> Date: Sunday, November 1, 2015 at 8:24 AM
>> To: Zookeeper <de...@zookeeper.apache.org>
>> Subject: Test failure
>>
>> This test seems to be failing frequently in trunk, has anyone had a look at this:
>>
>> org.apache.zookeeper.test.ClientPortBindTest.testBindByAddress
>>
>> Error Details
>>
>> Forked Java VM exited abnormally. Please note the time in the report does not reflect the time until the VM exit.
>>
>> Stack Trace
>>
>>
>> -Flavio
Re: Test failure
Posted by Michi Mutsuzaki <mu...@gmail.com>.
Chris, which log file are you looking at? I looked at
https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper-trunk/2806/consoleFull
and it seems to be using Oracle JDK 1.7.0-64.
[junit] 2015-11-01 11:04:05,246 [myid:] - INFO
[main:Environment@109] - Server environment:java.version=1.7.0
[junit] 2015-11-01 11:04:05,249 [myid:] - INFO
[main:Environment@109] - Server environment:java.vendor=Oracle
Corporation
[junit] 2015-11-01 11:04:05,249 [myid:] - INFO
[main:Environment@109] - Server
environment:java.home=/home/jenkins/tools/java/jdk1.7.0-64/jre
On Sun, Nov 1, 2015 at 1:49 PM, Chris Nauroth <cn...@hortonworks.com> wrote:
>
> Digging into the console log, I found evidence of a memory corruption error at the JVM level.
>
> [exec] [junit] Running org.apache.zookeeper.test.ClientPortBindTest in thread 2
> [exec] [junit] 2015-10-31 22:43:13,546 [myid:] - INFO [main:JUnit4ZKTestRunner@47] - No test.method specified. using default methods.
> [exec] [junit] 2015-10-31 22:43:13,558 [myid:] - INFO [main:ZKTestCase$1@55] - STARTING testBindByAddress
> [exec] [junit] 2015-10-31 22:43:13,559 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@77] - RUNNING TEST METHOD testBindByAddress
> [exec] [junit] *** Error in `/home/jenkins/tools/java/jdk1.7.0-64/jre/bin/java': malloc(): memory corruption: 0x00007ffc2c31e220 ***
> [exec] [junit] Test org.apache.zookeeper.test.ClientPortBindTest FAILED (crashed)
> [exec] [junit] Running org.apache.zookeeper.test.ClientPortBindTest in thread 2
> [exec] [junit] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 sec, Thread: 2, Class: org.apache.zookeeper.test.ClientPortBindTest
>
> That's odd. ClientPortBindTest is purely a Java test. We aren't doing JNI or anything.
>
> The test calls NetworkInterface.getNetworkInterfaces(). Looking through JDK bug reports, I see that there have been memory management bugs in this method.
>
> https://bugs.openjdk.java.net/browse/JDK-7075227
>
> https://bugs.openjdk.java.net/browse/JDK-8013140
>
> https://bugs.openjdk.java.net/browse/JDK-8033146
>
> The console log also shows that we're running a fairly old version of Java 7.
>
> java version "1.7.0_25"
> Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
> Java HotSpot(TM) Server VM (build 23.25-b01, mixed mode)
>
> I cannot repro this in any of my own environments, including a Java 1.7.0_67 environment and a Java 1.8.0_45 environment.
>
> I think it's likely that we're looking at an old Java bug, not a problem in the ZooKeeper codebase. If others agree, then I can file an INFRA JIRA to ask them for an upgrade to the latest Java 7 revision on our Jenkins hosts.
>
> --Chris Nauroth
>
> From: Flavio Junqueira <fp...@apache.org>
> Reply-To: Zookeeper <de...@zookeeper.apache.org>
> Date: Sunday, November 1, 2015 at 8:24 AM
> To: Zookeeper <de...@zookeeper.apache.org>
> Subject: Test failure
>
> This test seems to be failing frequently in trunk, has anyone had a look at this:
>
> org.apache.zookeeper.test.ClientPortBindTest.testBindByAddress
>
> Error Details
>
> Forked Java VM exited abnormally. Please note the time in the report does not reflect the time until the VM exit.
>
> Stack Trace
>
>
> -Flavio
Re: Test failure
Posted by Chris Nauroth <cn...@hortonworks.com>.
Digging into the console log, I found evidence of a memory corruption error at the JVM level.
[exec] [junit] Running org.apache.zookeeper.test.ClientPortBindTest in thread 2
[exec] [junit] 2015-10-31 22:43:13,546 [myid:] - INFO [main:JUnit4ZKTestRunner@47] - No test.method specified. using default methods.
[exec] [junit] 2015-10-31 22:43:13,558 [myid:] - INFO [main:ZKTestCase$1@55] - STARTING testBindByAddress
[exec] [junit] 2015-10-31 22:43:13,559 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@77] - RUNNING TEST METHOD testBindByAddress
[exec] [junit] *** Error in `/home/jenkins/tools/java/jdk1.7.0-64/jre/bin/java': malloc(): memory corruption: 0x00007ffc2c31e220 ***
[exec] [junit] Test org.apache.zookeeper.test.ClientPortBindTest FAILED (crashed)
[exec] [junit] Running org.apache.zookeeper.test.ClientPortBindTest in thread 2
[exec] [junit] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 sec, Thread: 2, Class: org.apache.zookeeper.test.ClientPortBindTest
That's odd. ClientPortBindTest is purely a Java test. We aren't doing JNI or anything.
The test calls NetworkInterface.getNetworkInterfaces(). Looking through JDK bug reports, I see that there have been memory management bugs in this method.
https://bugs.openjdk.java.net/browse/JDK-7075227
https://bugs.openjdk.java.net/browse/JDK-8013140
https://bugs.openjdk.java.net/browse/JDK-8033146
The console log also shows that we're running a fairly old version of Java 7.
java version "1.7.0_25"
Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
Java HotSpot(TM) Server VM (build 23.25-b01, mixed mode)
I cannot repro this in any of my own environments, including a Java 1.7.0_67 environment and a Java 1.8.0_45 environment.
I think it's likely that we're looking at an old Java bug, not a problem in the ZooKeeper codebase. If others agree, then I can file an INFRA JIRA to ask them for an upgrade to the latest Java 7 revision on our Jenkins hosts.
--Chris Nauroth
From: Flavio Junqueira <fp...@apache.org>>
Reply-To: Zookeeper <de...@zookeeper.apache.org>>
Date: Sunday, November 1, 2015 at 8:24 AM
To: Zookeeper <de...@zookeeper.apache.org>>
Subject: Test failure
This test seems to be failing frequently in trunk, has anyone had a look at this:
org.apache.zookeeper.test.ClientPortBindTest.testBindByAddress<https://builds.apache.org/view/All/job/ZooKeeper-trunk/2803/testReport/org.apache.zookeeper.test/ClientPortBindTest/testBindByAddress/>
[cid:429F009F-4D21-4A1F-AC3F-6164CF19DC0D@home] Error Details
Forked Java VM exited abnormally. Please note the time in the report does not reflect the time until the VM exit.
[cid:69D1E67F-567C-4206-93ED-970DBD884C8D@home] Stack Trace
-Flavio