uest based on what I have so far.
Kind Regards,
Martin.
-Original Message-
From: Tibor Digana
Sent: 09 July 2020 12:05
To: Maven Users List
Subject: Re: Surefire - Forking - Identifying Tests that run in a particular
fork
Thank you Martin for your ideas.
I have expected this goal
functionality doesn't provide a mechanism for this out of the box
> then it would be highly desirable for it to do so based on the reasons
> outlined; of course, if the fork mechanism already supports doing this then
> it would be great to hear how to configure Surefire in order to get this
&
To: martin.lambe...@ntlworld.com.invalid
Cc: Maven Users List
Subject: Re: Surefire - Forking - Identifying Tests that run in a particular
fork
Hi Martin,
Can you be more concrete with your business expectations?
What logger, what kind of notations about forked JVM id you want to express in
th
rs-custom
> (it really does just involve creating the specific file in the location
> mentioned, containing only the fully qualified name of your
> TestExecutionListener class 😊 ).
>
> Cheers,
>
> Martin.
>
> -Original Message-
> From: Falko Modler
> Sent:
mentioned, containing only the fully qualified name of your
TestExecutionListener class 😊 ).
Cheers,
Martin.
-Original Message-
From: Falko Modler
Sent: 01 July 2020 23:48
To: users@maven.apache.org
Subject: Re: Surefire - Forking - Identifying Tests that run in a particular
fork
Hi Mar
Hi Martin,
OOTB you'll probably have to resort to -X (which logs way too much) and
even then I am not 100% sure you'll get what you need.
Did you have a look at |${surefire.forkNumber}| (see
https://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html
Hello,
I'm currently using the Surefire plugin with Maven 3.6.3 and would like to
know if there is any way to identify what tests were run in a given fork? I
haven't seen any option for it in the current documentation. I'm running
around ~10K test cases hence using the fork option to speed thin
No special treatment for file.encoding? OK, that answers that. One
might have thought that the plugin running the show and the forked JVM
needed to be on the same (code)page.
On Fri, May 21, 2010 at 3:47 PM, Stephen Connolly
wrote:
> not
>
> you need to define what system properties to pass throu
not
you need to define what system properties to pass through in the wrote:
> If I set -Dfile.encoding=utf8 in my MAVEN_OPTS, should I expect forked
> JVMs from surefire to inherit this, or not?
>
> -
> To unsubscribe, e-mail: u
If I set -Dfile.encoding=utf8 in my MAVEN_OPTS, should I expect forked
JVMs from surefire to inherit this, or not?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apac
My coworker just found out that version 2.0 of surefire shows the correct
error msgs.So it seems that error handling was changed between them and now
it swallows the correct exceptions :-/
That would have saved a lot of time debugging this lol.
On Wed, Apr 8, 2009 at 7:45 AM, Tim wrote:
> That's
That's good to know :)
I can double check but that is probably not what is happening here since it
is defined in the parent pom as junit 4.
On Wed, Apr 8, 2009 at 7:15 AM, Jörg Schaible wrote:
> Hi Tim,
>
> Tim wrote at Mittwoch, 8. April 2009 14:05:
>
> > Unfortunately not. It seems however tha
Hi Tim,
Tim wrote at Mittwoch, 8. April 2009 14:05:
> Unfortunately not. It seems however that surefire is actually giving the
> wrong stacktrace.
> When I run this via the cli using the classpath that surefire says it is
> using I get a different exception.
> It seems that a dependency was missi
Unfortunately not. It seems however that surefire is actually giving the
wrong stacktrace.
When I run this via the cli using the classpath that surefire says it is
using I get a different exception.
It seems that a dependency was missing at that point. When I added it, I got
a new exception instead
Is there more of a trace supplied from within Surefire? Have you
searched to see if anyone else encountered this problem?
Thanks,
Brett
On 08/04/2009, at 10:47 AM, Tim wrote:
yea the tmp files look fine. In fact I see the correct junit jar
version and
all the dependency jars correctly in t
yea the tmp files look fine. In fact I see the correct junit jar version and
all the dependency jars correctly in them.Still, I have no clue why it can't
find a test class directly in it's classpath.
On Tue, Apr 7, 2009 at 7:35 PM, Brett Porter wrote:
> That sounds like a separate problem, howev
That sounds like a separate problem, however I can't tell what is
wrong from the info here. Are you able to check the surefire temporary
files to see if the arguments look reasonable?
- Brett
On 08/04/2009, at 10:27 AM, Tim wrote:
It doesn't show the junit 3 jar but has the same problem:
It doesn't show the junit 3 jar but has the same problem:
Forking command line: /bin/sh -c cd /home/tich/data/bps_trunk/bps-api &&
/usr/lib/jvm/jdk1.6.0_13/jre/bin/java -jar
/tmp/surefirebooter2137625950913122347.jar
/tmp/surefire4278370938049229367tmp /tmp/surefire3389360321643705255tmp
org.apach
Can you try the latest version of the surefire plugin? (v2.4.3)
On 08/04/2009, at 10:15 AM, Tim wrote:
Yea. It's showing up as [INFO]junit:junit:jar:4.4:test with no
version 3
in the list.This is with maven 2.1.0 AND 2.0.10 btw.
The reason that I noticed this was because I have a base tes
Yea. It's showing up as [INFO]junit:junit:jar:4.4:test with no version 3
in the list.This is with maven 2.1.0 AND 2.0.10 btw.
The reason that I noticed this was because I have a base test class in a
dependency that surefire was not able to find. But compilation was fine.
On Tue, Apr 7, 2009 at
have you confirmed that dependency:list only shows junit 4?
On 08/04/2009, at 9:18 AM, Tim wrote:
Why do I see
Forking command line: /usr/lib/jvm/jdk1.6.0_13/jre/bin/java -classpath
/home/tich/.m2/repository/org/apache/maven/surefire/surefire-booter/
2.3/surefire-booter-2.3.jar:/home/tich/.m2
Why do I see
Forking command line: /usr/lib/jvm/jdk1.6.0_13/jre/bin/java -classpath
/home/tich/.m2/repository/org/apache/maven/surefire/surefire-booter/2.3/surefire-booter-2.3.jar:/home/tich/.m2/repository/org/apache/maven/surefire/surefire-api/2.3/surefire-api-2.3.jar:/home/tich/.m2/repository/or
We have surefire forking 90% working in a testing version (see
instructions on the website for how to test dev versions of plugins)
- Brett
On 12/9/05, Tim Waters <[EMAIL PROTECTED]> wrote:
> Actually, we do not having forking available, so the "-
> Dsurefire.forkMode=
Actually, we do not having forking available, so the "-
Dsurefire.forkMode=once" flag is not applicable for our version of Maven 2.0.
Going to patch surefire soon. I'll respond to this thread if the patch
works.
On 12/8/05, Tim Waters <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I'm having trouble with
Hi,
I'm having trouble with Maven when using CORBA. I have a unit test which
uses a third-party re-implementation of a java class
(org/omg/CORBA/portable/Streamable). I've seen discussion in the past for
Ant-- that this type of problem is resolved by setting "fork" equal to
"true", however what
ncies..).
On a UNIX box, I do have a different error:
"Embedded error: Error while executing forked tests.
-classpath: not found"
Regards,
Jérôme.
2005/12/4, Jason van Zyl <[EMAIL PROTECTED]>:
Hi,
If anyone wants to try the new code for surefire forking a snapshot
plugin is av
dependencies..).
On a UNIX box, I do have a different error:
"Embedded error: Error while executing forked tests.
-classpath: not found"
Regards,
Jérôme.
2005/12/4, Jason van Zyl <[EMAIL PROTECTED]>:
Hi,
If anyone wants to try the new code for surefire forking a snapshot
plugin is a
TED]>:
Hi,
If anyone wants to try the new code for surefire forking a snapshot
plugin is available. Please refer to this guide to get yourself going:
http://maven.apache.org/guides/development/guide-testing-development-plugins.html
--
jvz.
Jason van Zyl
jason at maven.org
http://maven.ap
on van Zyl <[EMAIL PROTECTED]>:
>
> Hi,
>
> If anyone wants to try the new code for surefire forking a snapshot
> plugin is available. Please refer to this guide to get yourself going:
>
>
> http://maven.apache.org/guides/development/guide-testing-development-plugins.html
&
Hi,
If anyone wants to try the new code for surefire forking a snapshot
plugin is available. Please refer to this guide to get yourself going:
http://maven.apache.org/guides/development/guide-testing-development-plugins.html
--
jvz.
Jason van Zyl
jason at maven.org
http://maven.apache.org
30 matches
Mail list logo