Chris,
It might point to a bug in jtreg, or just "bad" jtreg meta-data.
>: ls one
... HelloWorld.java
>: cat one/HelloWorld.java
/*
* @test
* @bug 8765432
*/
/*
* @test
*/
public class HelloWorld {
public static void main(String[] args) {
ist) but the other one wasn't?
Thanks,
iris
-Original Message-
From: Chris Hegarty
Sent: Friday, August 02, 2013 3:19 AM
To: Paul Sandoz
Cc: Core-Libs-Dev Core-Libs-Dev
Subject: Re: Remove superfluous @test tags from
SpliteratorTraversingAndSplittingTest
On 02/08/2013 10:52, Paul Sand
s
been somehow excluded (e.g. on a problem list) but the other one wasn't?
Thanks,
iris
-Original Message-
From: Chris Hegarty
Sent: Friday, August 02, 2013 3:19 AM
To: Paul Sandoz
Cc: Core-Libs-Dev Core-Libs-Dev
Subject: Re: Remove superfluous @test tags from
SpliteratorTraversingAndSpl
hanks,
iris
-Original Message-
From: Chris Hegarty
Sent: Friday, August 02, 2013 3:19 AM
To: Paul Sandoz
Cc: Core-Libs-Dev Core-Libs-Dev
Subject: Re: Remove superfluous @test tags from
SpliteratorTraversingAndSplittingTest
On 02/08/2013 10:52, Paul Sandoz wrote:
>
>
On 02/08/2013 10:52, Paul Sandoz wrote:
On Aug 2, 2013, at 9:59 AM, Chris Hegarty wrote:
SpliteratorTraversingAndSplittingTest contains two @test tags. The second of
which does not specify that the test needs to run with testng. This causes the
test to fail, or have an error, when run as a
On Aug 2, 2013, at 9:59 AM, Chris Hegarty wrote:
> SpliteratorTraversingAndSplittingTest contains two @test tags. The second of
> which does not specify that the test needs to run with testng. This causes
> the test to fail, or have an error, when run as a batch with other tests.
>
> The seco
SpliteratorTraversingAndSplittingTest contains two @test tags. The
second of which does not specify that the test needs to run with testng.
This causes the test to fail, or have an error, when run as a batch with
other tests.
The second @test tag is just not needed, and the @bug should be move
