You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Oliver Geisser <ol...@gmail.com> on 2007/02/22 23:22:56 UTC

Allways two errors in tapestry-core tests

Hi,

does anyone else experience the following two errors in tapestry-core tests?

Environment:

JDK 1.5
Maven 2.0.5
Tapestry 5 Core checked out from trunk


[...]
Results :

Failed tests:
  org.apache.tapestry.corelib.components.OutputTest.simple_output(
org.apache.tapestry.corelib.components.OutputTest.simple_output)
org.apache.tapestry.corelib.components.OutputTest.output_with_element_and_informals
(
org.apache.tapestry.corelib.components.OutputTest.output_with_element_and_informals
)

Tests run: 753, Failures: 2, Errors: 0, Skipped: 0

I'm quite curious if this is a problem with my environment?


-- 
og

Re: Allways two errors in tapestry-core tests

Posted by Oliver Geisser <ol...@gmail.com>.
Hi,


On 2/25/07, Oliver Geisser <ol...@gmail.com> wrote:
>
> Hi.
>
> On 2/24/07, Howard Lewis Ship <hl...@gmail.com> wrote:Should have looked
> more closely; it's obvious to me that it's a locale
> issue. Need to use explcit locale in the tests.
>
>
>
> Yes, indeed. The tests are locale specific. It's testing for a locale
> dependant formated decimal number.
> Because I'm running a german windows the output is "22,70"and not the
> expected " 22.70".
>
>
> But now I have some other strange test results.
>
> Failed tests:
>   org.apache.tapestry.integration.IntegrationTests.password_field(
> org.apache.tapestry.integration.IntegrationTests.password_field )
> org.apache.tapestry.corelib.components.OutputTest.simple_output(
> org.apache.tapestry.corelib.components.OutputTest.simple_output)
>
> org.apache.tapestry.corelib.components.OutputTest.output_with_element_and_informals(
>
> org.apache.tapestry.corelib.components.OutputTest.output_with_element_and_informals
> )
>
> org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
> (
> org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url)
>
> org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
> (
> org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
> )
>
> org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url(
> org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
> )
>
> org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
> (
> org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url)
>
> org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
> (
> org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
> )
>
> org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path(
> org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path
> )
>
> org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path
> (
> org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path)
>
> org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path
> (
> org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path
> )
>
> org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path(
> org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path
> )
>
> org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path
> (
> org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path)
>
> The OutputTest tests fail because of the locale settings. OK.
>
> But the other ones show a strange behaviour.
>
> The IntegrationTests.password_field test does not allways fail - only
> sometime. Seems like a timing problem?
>
> The ClasspathAssetAliasManagerImplTest test only fail if they are run from
> maven!?
> If I start them with "mvn test" (on the command line or with the Eclipse
> Maven plugin) they fail.
> If I start the tests with the TestNG Eclipse plugin they do not fail.
>
>
anwering myself I just want to tell that one of the last commits fixed the
ClasspathAssetAliasManagerImplTest failures.for me.

Together with the patch from issue TAPESTRY-1300  I now can build ("mvn
clean install") the tapestry-project (and submodules) without any errors.
Great ;-)

BTW What's the state of the tapestry-workbench module? I assume it is not up
to date by intention!?


-- 
og

Re: Allways two errors in tapestry-core tests

Posted by Oliver Geisser <ol...@gmail.com>.
Hi.

On 2/24/07, Howard Lewis Ship <hl...@gmail.com> wrote:Should have looked
more closely; it's obvious to me that it's a locale
issue. Need to use explcit locale in the tests.



Yes, indeed. The tests are locale specific. It's testing for a locale
dependant formated decimal number.
Because I'm running a german windows the output is "22,70"and not the
expected "22.70".


But now I have some other strange test results.

Failed tests:
  org.apache.tapestry.integration.IntegrationTests.password_field(
org.apache.tapestry.integration.IntegrationTests.password_field)
org.apache.tapestry.corelib.components.OutputTest.simple_output(
org.apache.tapestry.corelib.components.OutputTest.simple_output)
org.apache.tapestry.corelib.components.OutputTest.output_with_element_and_informals
(
org.apache.tapestry.corelib.components.OutputTest.output_with_element_and_informals
)
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
(
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
)
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
(
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
)
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
(
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
)
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
(
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
)
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
(
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_client_url
)
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path
(
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path
)
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path
(
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path
)
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path
(
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path
)
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path
(
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path
)
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path
(
org.apache.tapestry.internal.services.ClasspathAssetAliasManagerImplTest.to_resource_path
)

The OutputTest tests fail because of the locale settings. OK.

But the other ones show a strange behaviour.

The IntegrationTests.password_field test does not allways fail - only
sometime. Seems like a timing problem?

The ClasspathAssetAliasManagerImplTest test only fail if they are run from
maven!?
If I start them with "mvn test" (on the command line or with the Eclipse
Maven plugin) they fail.
If I start the tests with the TestNG Eclipse plugin they do not fail.

Anyone else seeing similliar effects?

BTW
How can I debug the tests with Eclipse while running from the Eclipse Maven
plugin?

-- 
og

Re: Allways two errors in tapestry-core tests

Posted by Howard Lewis Ship <hl...@gmail.com>.
Should have looked more closely; it's obvious to me that it's a locale
issue. Need to use explcit locale in the tests.

On 2/23/07, Alejandro Scandroli <al...@gmail.com> wrote:
> Same here.
>
> Environment:
> svn rev  511168
> Ubuntu Edgy 64 (6.10)
> Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_10-b03, mixed mode)
> Maven version: 2.0.5
>
> Results :
>
> Failed tests:
> org.apache.tapestry.corelib.components.OutputTest.simple_output(org.apache.tapestry.corelib.components.OutputTest.simple_output)
> org.apache.tapestry.corelib.components.OutputTest.output_with_element_and_informals(org.apache.tapestry.corelib.components.OutputTest.output_with_element_and_informals)
>
> Tests run: 762, Failures: 2, Errors: 0, Skipped: 0
>
>
> Alejandro.
>
> On 2/23/07, Howard Lewis Ship <hl...@gmail.com> wrote:
> > It's likely a line termination error; I work on Mac OS X and Bamboo is
> > running on Linux.
> >
> > I'll switch over to my Windows box and check it out when I get a chance.
> >
> > On 2/22/07, D&J Gredler <dj...@gmail.com> wrote:
> > > Haven't tried it myself lately, but Bamboo just built without a problem :-)
> > >
> > >
> > > On 2/22/07, Oliver Geisser <ol...@gmail.com> wrote:
> > > >
> > > > Hi,
> > > >
> > > > does anyone else experience the following two errors in tapestry-core
> > > > tests?
> > > >
> > > > Environment:
> > > >
> > > > JDK 1.5
> > > > Maven 2.0.5
> > > > Tapestry 5 Core checked out from trunk
> > > >
> > > >
> > > > [...]
> > > > Results :
> > > >
> > > > Failed tests:
> > > >   org.apache.tapestry.corelib.components.OutputTest.simple_output(
> > > > org.apache.tapestry.corelib.components.OutputTest.simple_output)
> > > >
> > > > org.apache.tapestry.corelib.components.OutputTest.output_with_element_and_informals
> > > > (
> > > >
> > > > org.apache.tapestry.corelib.components.OutputTest.output_with_element_and_informals
> > > > )
> > > >
> > > > Tests run: 753, Failures: 2, Errors: 0, Skipped: 0
> > > >
> > > > I'm quite curious if this is a problem with my environment?
> > > >
> > > >
> > > > --
> > > > og
> > > >
> > >
> >
> >
> > --
> > Howard M. Lewis Ship
> > TWD Consulting, Inc.
> > Independent J2EE / Open-Source Java Consultant
> > Creator and PMC Chair, Apache Tapestry
> > Creator, Apache HiveMind
> >
> > Professional Tapestry training, mentoring, support
> > and project work.  http://howardlewisship.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>


-- 
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind

Professional Tapestry training, mentoring, support
and project work.  http://howardlewisship.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Re: Allways two errors in tapestry-core tests

Posted by Alejandro Scandroli <al...@gmail.com>.
Same here.

Environment:
svn rev  511168
Ubuntu Edgy 64 (6.10)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_10-b03, mixed mode)
Maven version: 2.0.5

Results :

Failed tests:
org.apache.tapestry.corelib.components.OutputTest.simple_output(org.apache.tapestry.corelib.components.OutputTest.simple_output)
org.apache.tapestry.corelib.components.OutputTest.output_with_element_and_informals(org.apache.tapestry.corelib.components.OutputTest.output_with_element_and_informals)

Tests run: 762, Failures: 2, Errors: 0, Skipped: 0


Alejandro.

On 2/23/07, Howard Lewis Ship <hl...@gmail.com> wrote:
> It's likely a line termination error; I work on Mac OS X and Bamboo is
> running on Linux.
>
> I'll switch over to my Windows box and check it out when I get a chance.
>
> On 2/22/07, D&J Gredler <dj...@gmail.com> wrote:
> > Haven't tried it myself lately, but Bamboo just built without a problem :-)
> >
> >
> > On 2/22/07, Oliver Geisser <ol...@gmail.com> wrote:
> > >
> > > Hi,
> > >
> > > does anyone else experience the following two errors in tapestry-core
> > > tests?
> > >
> > > Environment:
> > >
> > > JDK 1.5
> > > Maven 2.0.5
> > > Tapestry 5 Core checked out from trunk
> > >
> > >
> > > [...]
> > > Results :
> > >
> > > Failed tests:
> > >   org.apache.tapestry.corelib.components.OutputTest.simple_output(
> > > org.apache.tapestry.corelib.components.OutputTest.simple_output)
> > >
> > > org.apache.tapestry.corelib.components.OutputTest.output_with_element_and_informals
> > > (
> > >
> > > org.apache.tapestry.corelib.components.OutputTest.output_with_element_and_informals
> > > )
> > >
> > > Tests run: 753, Failures: 2, Errors: 0, Skipped: 0
> > >
> > > I'm quite curious if this is a problem with my environment?
> > >
> > >
> > > --
> > > og
> > >
> >
>
>
> --
> Howard M. Lewis Ship
> TWD Consulting, Inc.
> Independent J2EE / Open-Source Java Consultant
> Creator and PMC Chair, Apache Tapestry
> Creator, Apache HiveMind
>
> Professional Tapestry training, mentoring, support
> and project work.  http://howardlewisship.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Re: Allways two errors in tapestry-core tests

Posted by Howard Lewis Ship <hl...@gmail.com>.
It's likely a line termination error; I work on Mac OS X and Bamboo is
running on Linux.

I'll switch over to my Windows box and check it out when I get a chance.

On 2/22/07, D&J Gredler <dj...@gmail.com> wrote:
> Haven't tried it myself lately, but Bamboo just built without a problem :-)
>
>
> On 2/22/07, Oliver Geisser <ol...@gmail.com> wrote:
> >
> > Hi,
> >
> > does anyone else experience the following two errors in tapestry-core
> > tests?
> >
> > Environment:
> >
> > JDK 1.5
> > Maven 2.0.5
> > Tapestry 5 Core checked out from trunk
> >
> >
> > [...]
> > Results :
> >
> > Failed tests:
> >   org.apache.tapestry.corelib.components.OutputTest.simple_output(
> > org.apache.tapestry.corelib.components.OutputTest.simple_output)
> >
> > org.apache.tapestry.corelib.components.OutputTest.output_with_element_and_informals
> > (
> >
> > org.apache.tapestry.corelib.components.OutputTest.output_with_element_and_informals
> > )
> >
> > Tests run: 753, Failures: 2, Errors: 0, Skipped: 0
> >
> > I'm quite curious if this is a problem with my environment?
> >
> >
> > --
> > og
> >
>


-- 
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind

Professional Tapestry training, mentoring, support
and project work.  http://howardlewisship.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Re: Allways two errors in tapestry-core tests

Posted by D&J Gredler <dj...@gmail.com>.
Haven't tried it myself lately, but Bamboo just built without a problem :-)


On 2/22/07, Oliver Geisser <ol...@gmail.com> wrote:
>
> Hi,
>
> does anyone else experience the following two errors in tapestry-core
> tests?
>
> Environment:
>
> JDK 1.5
> Maven 2.0.5
> Tapestry 5 Core checked out from trunk
>
>
> [...]
> Results :
>
> Failed tests:
>   org.apache.tapestry.corelib.components.OutputTest.simple_output(
> org.apache.tapestry.corelib.components.OutputTest.simple_output)
>
> org.apache.tapestry.corelib.components.OutputTest.output_with_element_and_informals
> (
>
> org.apache.tapestry.corelib.components.OutputTest.output_with_element_and_informals
> )
>
> Tests run: 753, Failures: 2, Errors: 0, Skipped: 0
>
> I'm quite curious if this is a problem with my environment?
>
>
> --
> og
>