You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Gary Gregory <ga...@gmail.com> on 2012/03/03 19:33:32 UTC
[lang] test failures
Hi All:
Odd: These pass in Eclipse but fail from Maven...
Failed tests:
testReflectionFloatArrayArray(org.apache.commons.lang3.builder.ToStringBuilderTest)
testReflectionDoubleArrayArray(org.apache.commons.lang3.builder.ToStringBuilderTest)
testReflectionBooleanArrayArray(org.apache.commons.lang3.builder.ToStringBuilderTest)
testReflectionHierarchyArrayList(org.apache.commons.lang3.builder.ToStringBuilderTest)
testReflectionArrayCycleLevel2(org.apache.commons.lang3.builder.ToStringBuilderTest)
testReflectionArrayArrayCycle(org.apache.commons.lang3.builder.ToStringBuilderTest)
testSimpleReflectionObjectCycle(org.apache.commons.lang3.builder.ToStringBuilderTest)
testSelfInstanceVarReflectionObjectCycle(org.apache.commons.lang3.builder.ToStringBuilderTest)
testSelfInstanceTwoVarsReflectionObjectCycle(org.apache.commons.lang3.builder.ToStringBuilderTest)
testReflectionArrayAndObjectCycle(org.apache.commons.lang3.builder.ToStringBuilderTest)
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: [lang] test failures
Posted by Stefan Bodewig <bo...@apache.org>.
On 2012-03-05, sebb wrote:
> The tests also fail in Gump.
vmgump.ao, gump.zones.ao and adam.ao run JDK 6 (vmgump uses OpenJDK, the
FreeBSD zone the FreeBSD port and adam the MacOS X version by Apple).
So it likely is not a Java7 issue.
Gump uses mvn2 to run the tests if that causes any difference. Also I
note the number of failing tests is different for each machine.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [lang] test failures
Posted by Jörg Schaible <Jo...@scalaris.com>.
sebb wrote:
> On 5 March 2012 17:11, sebb <se...@gmail.com> wrote:
>> On 5 March 2012 16:53, Jörg Schaible <Jo...@scalaris.com> wrote:
[snip]
>>>
>>> We might set the runOrder to "random" in the surefire plugin. This helps
>>> to ensure that tests will not have unwanted side effects.
>>
>> Good idea; I'll add that.
>
> On second thoughts, that won't help if the problem is the order of
> tests *within* a test class (as was the case for JMeter).
Yeah, I'd love to have that option too.
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [lang] test failures
Posted by sebb <se...@gmail.com>.
On 5 March 2012 17:11, sebb <se...@gmail.com> wrote:
> On 5 March 2012 16:53, Jörg Schaible <Jo...@scalaris.com> wrote:
>> sebb wrote:
>>
>>> On 5 March 2012 15:09, Benedikt Ritter <be...@systemoutprintln.de> wrote:
>>>> Am 05.03.2012 16:03, schrieb Benedikt Ritter:
>>>>
>>>>> Am 04.03.2012 12:26, schrieb Jörg Schaible:
>>>>>>
>>>>>> Benedikt Ritter wrote:
>>>>>>
>>>>>>> Just out of curiosity ;) Are there plans to do anything about that? I
>>>>>>> guess it would be desirable if the component compiles on Java 7 as
>>>>>>> well. I still don't know if things are broken when compiling with Java
>>>>>>> 7 or if the errors are just caused by API changes in Java 7. If the
>>>>>>> latter, we could use JUnit's Theories runner and write an assumeTrue()
>>>>>>> statement for those test cases, that checks what Java version the test
>>>>>>> is running with.
>>>>>>
>>>>>>
>>>>>> I am quite sure I voted on lang3 and that means I also tested it with
>>>>>> Java
>>>>>> 7. Actually I can build lang3 HEAD with Java 7:
>>>>>
>>>>>
>>>>> sorry, I'm not sure if I got you right. Are you saying that the problems
>>>>> Gary was experiencing are not a result of Java 7 usage? Then we should
>>>>> investigate further.
>>>>>
>>>>
>>>> I just checked out HEAD and run mvn test with my setup:
>>>>
>>>> D:\Entwicklung\workspaces\commons\lang>mvn -version
>>>> Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
>>>> Maven home: D:\Entwicklung\maven\3.0.3
>>>> Java version: 1.7.0_01, vendor: Oracle Corporation
>>>> Java home: D:\Entwicklung\Java\jdk1.7.0_01\jre
>>>> Default locale: de_DE, platform encoding: Cp1252
>>>> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>>>>
>>>> I got the same result as Jörg. Gary, maybe you should have another look
>>>> at that issue?
>>>>
>>>> Regards,
>>>> Benedikt
>>>
>>> The tests also fail in Gump.
>>> I've tweaked the assertion to try and help a bit.
>>>
>>> Had a possibly similar situation in JMeter recently; only the Gump build
>>> failed. Turned out that the tests were being run in a different order by
>>> the Gump JVM; this revealed a test bug which was failing to clear up data
>>> from a previous test.
>>
>>
>> We might set the runOrder to "random" in the surefire plugin. This helps to
>> ensure that tests will not have unwanted side effects.
>
> Good idea; I'll add that.
On second thoughts, that won't help if the problem is the order of
tests *within* a test class (as was the case for JMeter).
> I've just added some checks to see that the data is not present before
> the test starts.
>
> BTW the JMeter test used Maven; it was the JVM which permuted the test order.
>
>> - Jörg
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [lang] test failures
Posted by sebb <se...@gmail.com>.
On 5 March 2012 16:53, Jörg Schaible <Jo...@scalaris.com> wrote:
> sebb wrote:
>
>> On 5 March 2012 15:09, Benedikt Ritter <be...@systemoutprintln.de> wrote:
>>> Am 05.03.2012 16:03, schrieb Benedikt Ritter:
>>>
>>>> Am 04.03.2012 12:26, schrieb Jörg Schaible:
>>>>>
>>>>> Benedikt Ritter wrote:
>>>>>
>>>>>> Just out of curiosity ;) Are there plans to do anything about that? I
>>>>>> guess it would be desirable if the component compiles on Java 7 as
>>>>>> well. I still don't know if things are broken when compiling with Java
>>>>>> 7 or if the errors are just caused by API changes in Java 7. If the
>>>>>> latter, we could use JUnit's Theories runner and write an assumeTrue()
>>>>>> statement for those test cases, that checks what Java version the test
>>>>>> is running with.
>>>>>
>>>>>
>>>>> I am quite sure I voted on lang3 and that means I also tested it with
>>>>> Java
>>>>> 7. Actually I can build lang3 HEAD with Java 7:
>>>>
>>>>
>>>> sorry, I'm not sure if I got you right. Are you saying that the problems
>>>> Gary was experiencing are not a result of Java 7 usage? Then we should
>>>> investigate further.
>>>>
>>>
>>> I just checked out HEAD and run mvn test with my setup:
>>>
>>> D:\Entwicklung\workspaces\commons\lang>mvn -version
>>> Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
>>> Maven home: D:\Entwicklung\maven\3.0.3
>>> Java version: 1.7.0_01, vendor: Oracle Corporation
>>> Java home: D:\Entwicklung\Java\jdk1.7.0_01\jre
>>> Default locale: de_DE, platform encoding: Cp1252
>>> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>>>
>>> I got the same result as Jörg. Gary, maybe you should have another look
>>> at that issue?
>>>
>>> Regards,
>>> Benedikt
>>
>> The tests also fail in Gump.
>> I've tweaked the assertion to try and help a bit.
>>
>> Had a possibly similar situation in JMeter recently; only the Gump build
>> failed. Turned out that the tests were being run in a different order by
>> the Gump JVM; this revealed a test bug which was failing to clear up data
>> from a previous test.
>
>
> We might set the runOrder to "random" in the surefire plugin. This helps to
> ensure that tests will not have unwanted side effects.
Good idea; I'll add that.
I've just added some checks to see that the data is not present before
the test starts.
BTW the JMeter test used Maven; it was the JVM which permuted the test order.
> - Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [lang] test failures
Posted by Jörg Schaible <Jo...@scalaris.com>.
sebb wrote:
> On 5 March 2012 15:09, Benedikt Ritter <be...@systemoutprintln.de> wrote:
>> Am 05.03.2012 16:03, schrieb Benedikt Ritter:
>>
>>> Am 04.03.2012 12:26, schrieb Jörg Schaible:
>>>>
>>>> Benedikt Ritter wrote:
>>>>
>>>>> Just out of curiosity ;) Are there plans to do anything about that? I
>>>>> guess it would be desirable if the component compiles on Java 7 as
>>>>> well. I still don't know if things are broken when compiling with Java
>>>>> 7 or if the errors are just caused by API changes in Java 7. If the
>>>>> latter, we could use JUnit's Theories runner and write an assumeTrue()
>>>>> statement for those test cases, that checks what Java version the test
>>>>> is running with.
>>>>
>>>>
>>>> I am quite sure I voted on lang3 and that means I also tested it with
>>>> Java
>>>> 7. Actually I can build lang3 HEAD with Java 7:
>>>
>>>
>>> sorry, I'm not sure if I got you right. Are you saying that the problems
>>> Gary was experiencing are not a result of Java 7 usage? Then we should
>>> investigate further.
>>>
>>
>> I just checked out HEAD and run mvn test with my setup:
>>
>> D:\Entwicklung\workspaces\commons\lang>mvn -version
>> Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
>> Maven home: D:\Entwicklung\maven\3.0.3
>> Java version: 1.7.0_01, vendor: Oracle Corporation
>> Java home: D:\Entwicklung\Java\jdk1.7.0_01\jre
>> Default locale: de_DE, platform encoding: Cp1252
>> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>>
>> I got the same result as Jörg. Gary, maybe you should have another look
>> at that issue?
>>
>> Regards,
>> Benedikt
>
> The tests also fail in Gump.
> I've tweaked the assertion to try and help a bit.
>
> Had a possibly similar situation in JMeter recently; only the Gump build
> failed. Turned out that the tests were being run in a different order by
> the Gump JVM; this revealed a test bug which was failing to clear up data
> from a previous test.
We might set the runOrder to "random" in the surefire plugin. This helps to
ensure that tests will not have unwanted side effects.
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [lang] test failures
Posted by sebb <se...@gmail.com>.
On 5 March 2012 15:09, Benedikt Ritter <be...@systemoutprintln.de> wrote:
> Am 05.03.2012 16:03, schrieb Benedikt Ritter:
>
>> Am 04.03.2012 12:26, schrieb Jörg Schaible:
>>>
>>> Benedikt Ritter wrote:
>>>
>>>> Just out of curiosity ;) Are there plans to do anything about that? I
>>>> guess it would be desirable if the component compiles on Java 7 as well.
>>>> I still don't know if things are broken when compiling with Java 7 or if
>>>> the errors are just caused by API changes in Java 7. If the latter, we
>>>> could use JUnit's Theories runner and write an assumeTrue() statement
>>>> for those test cases, that checks what Java version the test is running
>>>> with.
>>>
>>>
>>> I am quite sure I voted on lang3 and that means I also tested it with
>>> Java
>>> 7. Actually I can build lang3 HEAD with Java 7:
>>
>>
>> sorry, I'm not sure if I got you right. Are you saying that the problems
>> Gary was experiencing are not a result of Java 7 usage? Then we should
>> investigate further.
>>
>
> I just checked out HEAD and run mvn test with my setup:
>
> D:\Entwicklung\workspaces\commons\lang>mvn -version
> Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
> Maven home: D:\Entwicklung\maven\3.0.3
> Java version: 1.7.0_01, vendor: Oracle Corporation
> Java home: D:\Entwicklung\Java\jdk1.7.0_01\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>
> I got the same result as Jörg. Gary, maybe you should have another look at
> that issue?
>
> Regards,
> Benedikt
The tests also fail in Gump.
I've tweaked the assertion to try and help a bit.
Had a possibly similar situation in JMeter recently; only the Gump build failed.
Turned out that the tests were being run in a different order by the
Gump JVM; this revealed a test bug which was failing to clear up data
from a previous test.
>
>>>
>>> ================= %< ==================
>>> $ mvn -version
>>> Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
>>> Maven home: /usr/share/maven-bin-3.0
>>> Java version: 1.7.0_03, vendor: Oracle Corporation
>>> Java home: /opt/oracle-jdk-bin-1.7.0.3/jre
>>> Default locale: en_US, platform encoding: UTF-8
>>> OS name: "linux", version: "3.2.1-gentoo-r2", arch: "amd64", family:
>>> "unix"
>>> ================= %< ==================
>>> Results :
>>>
>>> Tests run: 2139, Failures: 0, Errors: 0, Skipped: 4
>>> ================= %< ==================
>>>
>>>
>>> - Jörg
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [lang] test failures
Posted by Benedikt Ritter <be...@systemoutprintln.de>.
Am 05.03.2012 16:03, schrieb Benedikt Ritter:
> Am 04.03.2012 12:26, schrieb Jörg Schaible:
>> Benedikt Ritter wrote:
>>
>>> Just out of curiosity ;) Are there plans to do anything about that? I
>>> guess it would be desirable if the component compiles on Java 7 as well.
>>> I still don't know if things are broken when compiling with Java 7 or if
>>> the errors are just caused by API changes in Java 7. If the latter, we
>>> could use JUnit's Theories runner and write an assumeTrue() statement
>>> for those test cases, that checks what Java version the test is running
>>> with.
>>
>> I am quite sure I voted on lang3 and that means I also tested it with
>> Java
>> 7. Actually I can build lang3 HEAD with Java 7:
>
> sorry, I'm not sure if I got you right. Are you saying that the problems
> Gary was experiencing are not a result of Java 7 usage? Then we should
> investigate further.
>
I just checked out HEAD and run mvn test with my setup:
D:\Entwicklung\workspaces\commons\lang>mvn -version
Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
Maven home: D:\Entwicklung\maven\3.0.3
Java version: 1.7.0_01, vendor: Oracle Corporation
Java home: D:\Entwicklung\Java\jdk1.7.0_01\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
I got the same result as Jörg. Gary, maybe you should have another look
at that issue?
Regards,
Benedikt
>>
>> ================= %< ==================
>> $ mvn -version
>> Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
>> Maven home: /usr/share/maven-bin-3.0
>> Java version: 1.7.0_03, vendor: Oracle Corporation
>> Java home: /opt/oracle-jdk-bin-1.7.0.3/jre
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "linux", version: "3.2.1-gentoo-r2", arch: "amd64", family:
>> "unix"
>> ================= %< ==================
>> Results :
>>
>> Tests run: 2139, Failures: 0, Errors: 0, Skipped: 4
>> ================= %< ==================
>>
>>
>> - Jörg
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [lang] test failures
Posted by Gary Gregory <ga...@gmail.com>.
On Mon, Mar 5, 2012 at 10:03 AM, Benedikt Ritter
<be...@systemoutprintln.de>wrote:
> Am 04.03.2012 12:26, schrieb Jörg Schaible:
>
> Benedikt Ritter wrote:
>>
>> Just out of curiosity ;) Are there plans to do anything about that? I
>>> guess it would be desirable if the component compiles on Java 7 as well.
>>> I still don't know if things are broken when compiling with Java 7 or if
>>> the errors are just caused by API changes in Java 7. If the latter, we
>>> could use JUnit's Theories runner and write an assumeTrue() statement
>>> for those test cases, that checks what Java version the test is running
>>> with.
>>>
>>
>> I am quite sure I voted on lang3 and that means I also tested it with Java
>> 7. Actually I can build lang3 HEAD with Java 7:
>>
>
> sorry, I'm not sure if I got you right. Are you saying that the problems
> Gary was experiencing are not a result of Java 7 usage? Then we should
> investigate further.
This only happens on Java 7. I cannot look at this ATM.
Gary
>
>
>
>> ================= %< ==================
>> $ mvn -version
>> Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
>> Maven home: /usr/share/maven-bin-3.0
>> Java version: 1.7.0_03, vendor: Oracle Corporation
>> Java home: /opt/oracle-jdk-bin-1.7.0.3/**jre
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "linux", version: "3.2.1-gentoo-r2", arch: "amd64", family:
>> "unix"
>> ================= %< ==================
>> Results :
>>
>> Tests run: 2139, Failures: 0, Errors: 0, Skipped: 4
>> ================= %< ==================
>>
>>
>> - Jörg
>>
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.**apache.org<de...@commons.apache.org>
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@commons.**apache.org<de...@commons.apache.org>
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: [lang] test failures
Posted by Benedikt Ritter <be...@systemoutprintln.de>.
Am 04.03.2012 12:26, schrieb Jörg Schaible:
> Benedikt Ritter wrote:
>
>> Just out of curiosity ;) Are there plans to do anything about that? I
>> guess it would be desirable if the component compiles on Java 7 as well.
>> I still don't know if things are broken when compiling with Java 7 or if
>> the errors are just caused by API changes in Java 7. If the latter, we
>> could use JUnit's Theories runner and write an assumeTrue() statement
>> for those test cases, that checks what Java version the test is running
>> with.
>
> I am quite sure I voted on lang3 and that means I also tested it with Java
> 7. Actually I can build lang3 HEAD with Java 7:
sorry, I'm not sure if I got you right. Are you saying that the problems
Gary was experiencing are not a result of Java 7 usage? Then we should
investigate further.
>
> ================= %< ==================
> $ mvn -version
> Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
> Maven home: /usr/share/maven-bin-3.0
> Java version: 1.7.0_03, vendor: Oracle Corporation
> Java home: /opt/oracle-jdk-bin-1.7.0.3/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.2.1-gentoo-r2", arch: "amd64", family: "unix"
> ================= %< ==================
> Results :
>
> Tests run: 2139, Failures: 0, Errors: 0, Skipped: 4
> ================= %< ==================
>
>
> - Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [lang] test failures
Posted by Jörg Schaible <jo...@gmx.de>.
Benedikt Ritter wrote:
> Just out of curiosity ;) Are there plans to do anything about that? I
> guess it would be desirable if the component compiles on Java 7 as well.
> I still don't know if things are broken when compiling with Java 7 or if
> the errors are just caused by API changes in Java 7. If the latter, we
> could use JUnit's Theories runner and write an assumeTrue() statement
> for those test cases, that checks what Java version the test is running
> with.
I am quite sure I voted on lang3 and that means I also tested it with Java
7. Actually I can build lang3 HEAD with Java 7:
================= %< ==================
$ mvn -version
Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Maven home: /usr/share/maven-bin-3.0
Java version: 1.7.0_03, vendor: Oracle Corporation
Java home: /opt/oracle-jdk-bin-1.7.0.3/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.2.1-gentoo-r2", arch: "amd64", family: "unix"
================= %< ==================
Results :
Tests run: 2139, Failures: 0, Errors: 0, Skipped: 4
================= %< ==================
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [lang] test failures
Posted by Benedikt Ritter <be...@systemoutprintln.de>.
Just out of curiosity ;) Are there plans to do anything about that? I
guess it would be desirable if the component compiles on Java 7 as well.
I still don't know if things are broken when compiling with Java 7 or if
the errors are just caused by API changes in Java 7. If the latter, we
could use JUnit's Theories runner and write an assumeTrue() statement
for those test cases, that checks what Java version the test is running
with.
Regards,
Benedikt
Am 03.03.2012 20:05, schrieb Gary Gregory:
> You're right! The build is OK with Java 6, but not 7.
>
> Thank you!
> Gary
>
> On Sat, Mar 3, 2012 at 1:42 PM, Benedikt Ritter<be...@systemoutprintln.de>wrote:
>
>> Hi Gary,
>>
>> that somehow reminds of a problem we had in BeanUtils2 (see
>> http://markmail.org/thread/**obtmhywxxeo2ykp7<http://markmail.org/thread/obtmhywxxeo2ykp7>).
>> Some tests were failing with my configuration, while they passed on Simos
>> machine. The problem was, that I'm using Java 7 and that seems to cause
>> problems with reflective operations on arrays.
>>
>> I would suggest that you at first make sure, that maven and eclipse are
>> using the same Java version. And that can be a bit tricky, if m2e mixes
>> some addition spice into you dev-setup-soup. There are several
>> configurations that come into play:
>>
>> - the jre eclipse is startet with
>> - the jdk the workspace uses as default
>> - the jdk maven uses
>> - the jdk m2e starts maven with
>>
>> HTH,
>> Benedikt
>>
>> Am 03.03.2012 19:33, schrieb Gary Gregory:
>>
>> Hi All:
>>>
>>> Odd: These pass in Eclipse but fail from Maven...
>>>
>>> Failed tests:
>>> testReflectionFloatArrayArray(**org.apache.commons.lang3.**
>>> builder.ToStringBuilderTest)
>>>
>>> testReflectionDoubleArrayArray**(org.apache.commons.lang3.**
>>> builder.ToStringBuilderTest)
>>>
>>> testReflectionBooleanArrayArra**y(org.apache.commons.lang3.**
>>> builder.ToStringBuilderTest)
>>>
>>> testReflectionHierarchyArrayLi**st(org.apache.commons.lang3.**
>>> builder.ToStringBuilderTest)
>>>
>>> testReflectionArrayCycleLevel2**(org.apache.commons.lang3.**
>>> builder.ToStringBuilderTest)
>>>
>>> testReflectionArrayArrayCycle(**org.apache.commons.lang3.**
>>> builder.ToStringBuilderTest)
>>>
>>> testSimpleReflectionObjectCycl**e(org.apache.commons.lang3.**
>>> builder.ToStringBuilderTest)
>>>
>>> testSelfInstanceVarReflectionO**bjectCycle(org.apache.commons.**
>>> lang3.builder.**ToStringBuilderTest)
>>>
>>> testSelfInstanceTwoVarsReflect**ionObjectCycle(org.apache.**
>>> commons.lang3.builder.**ToStringBuilderTest)
>>>
>>> testReflectionArrayAndObjectCy**cle(org.apache.commons.lang3.**
>>> builder.ToStringBuilderTest)
>>>
>>>
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.**apache.org<de...@commons.apache.org>
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [lang] test failures
Posted by Gary Gregory <ga...@gmail.com>.
You're right! The build is OK with Java 6, but not 7.
Thank you!
Gary
On Sat, Mar 3, 2012 at 1:42 PM, Benedikt Ritter <be...@systemoutprintln.de>wrote:
> Hi Gary,
>
> that somehow reminds of a problem we had in BeanUtils2 (see
> http://markmail.org/thread/**obtmhywxxeo2ykp7<http://markmail.org/thread/obtmhywxxeo2ykp7>).
> Some tests were failing with my configuration, while they passed on Simos
> machine. The problem was, that I'm using Java 7 and that seems to cause
> problems with reflective operations on arrays.
>
> I would suggest that you at first make sure, that maven and eclipse are
> using the same Java version. And that can be a bit tricky, if m2e mixes
> some addition spice into you dev-setup-soup. There are several
> configurations that come into play:
>
> - the jre eclipse is startet with
> - the jdk the workspace uses as default
> - the jdk maven uses
> - the jdk m2e starts maven with
>
> HTH,
> Benedikt
>
> Am 03.03.2012 19:33, schrieb Gary Gregory:
>
> Hi All:
>>
>> Odd: These pass in Eclipse but fail from Maven...
>>
>> Failed tests:
>> testReflectionFloatArrayArray(**org.apache.commons.lang3.**
>> builder.ToStringBuilderTest)
>>
>> testReflectionDoubleArrayArray**(org.apache.commons.lang3.**
>> builder.ToStringBuilderTest)
>>
>> testReflectionBooleanArrayArra**y(org.apache.commons.lang3.**
>> builder.ToStringBuilderTest)
>>
>> testReflectionHierarchyArrayLi**st(org.apache.commons.lang3.**
>> builder.ToStringBuilderTest)
>>
>> testReflectionArrayCycleLevel2**(org.apache.commons.lang3.**
>> builder.ToStringBuilderTest)
>>
>> testReflectionArrayArrayCycle(**org.apache.commons.lang3.**
>> builder.ToStringBuilderTest)
>>
>> testSimpleReflectionObjectCycl**e(org.apache.commons.lang3.**
>> builder.ToStringBuilderTest)
>>
>> testSelfInstanceVarReflectionO**bjectCycle(org.apache.commons.**
>> lang3.builder.**ToStringBuilderTest)
>>
>> testSelfInstanceTwoVarsReflect**ionObjectCycle(org.apache.**
>> commons.lang3.builder.**ToStringBuilderTest)
>>
>> testReflectionArrayAndObjectCy**cle(org.apache.commons.lang3.**
>> builder.ToStringBuilderTest)
>>
>>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@commons.**apache.org<de...@commons.apache.org>
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: [lang] test failures
Posted by Benedikt Ritter <be...@systemoutprintln.de>.
Hi Gary,
that somehow reminds of a problem we had in BeanUtils2 (see
http://markmail.org/thread/obtmhywxxeo2ykp7). Some tests were failing
with my configuration, while they passed on Simos machine. The problem
was, that I'm using Java 7 and that seems to cause problems with
reflective operations on arrays.
I would suggest that you at first make sure, that maven and eclipse are
using the same Java version. And that can be a bit tricky, if m2e mixes
some addition spice into you dev-setup-soup. There are several
configurations that come into play:
- the jre eclipse is startet with
- the jdk the workspace uses as default
- the jdk maven uses
- the jdk m2e starts maven with
HTH,
Benedikt
Am 03.03.2012 19:33, schrieb Gary Gregory:
> Hi All:
>
> Odd: These pass in Eclipse but fail from Maven...
>
> Failed tests:
> testReflectionFloatArrayArray(org.apache.commons.lang3.builder.ToStringBuilderTest)
>
> testReflectionDoubleArrayArray(org.apache.commons.lang3.builder.ToStringBuilderTest)
>
> testReflectionBooleanArrayArray(org.apache.commons.lang3.builder.ToStringBuilderTest)
>
> testReflectionHierarchyArrayList(org.apache.commons.lang3.builder.ToStringBuilderTest)
>
> testReflectionArrayCycleLevel2(org.apache.commons.lang3.builder.ToStringBuilderTest)
>
> testReflectionArrayArrayCycle(org.apache.commons.lang3.builder.ToStringBuilderTest)
>
> testSimpleReflectionObjectCycle(org.apache.commons.lang3.builder.ToStringBuilderTest)
>
> testSelfInstanceVarReflectionObjectCycle(org.apache.commons.lang3.builder.ToStringBuilderTest)
>
> testSelfInstanceTwoVarsReflectionObjectCycle(org.apache.commons.lang3.builder.ToStringBuilderTest)
>
> testReflectionArrayAndObjectCycle(org.apache.commons.lang3.builder.ToStringBuilderTest)
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org