[jira] [Updated] (SUREFIRE-1237) Running suites forked
[ https://issues.apache.org/jira/browse/SUREFIRE-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koen Serneels updated SUREFIRE-1237: Description: I have a Maven module in which I grouped test classes based on their package into different TestNG suite files. The different suite's are listed in the plugin config using . The tests identified by the suites are ran sequentially ootb by surefire. With the current version it is already possible to run the tests within the suites in parallel using multiple threads (within a single JVM). However, in my situation I need them to run forked in different JMVs. So what I want is a JVM fork per suite XML file and not multiple threads. While there are also fork options, they don't seem to work in combination with suite XML files (but rather with methods and or test classes). So, what I'm after is an option that creates a pool of forked JVM's which takes care of running the available suite XML files. For ex. "suites 8". Each fork will then execute it's test (as identified by the suite XML file) in sequence. So for example, in the config given above, there will be 8 forked JVM's. When I have 10 suite XML files, each JVM will start working on the tests identified by its assigned suite XML. So, JVM1 will run all tests (sequentially) identified by suite XML1. In parallel, JVM2-8 will do the same thing for their assigned suite XML. From the moment a forked JVM is done processing its suite XML file it will start on the next one until they are all processed. was: At the moment I grouped the test classes of a Maven module into different TestNG suite files based on some criteria. The different suite's are ran sequentially ootb by surefire. With the current version it is possible to run the suites in parallel using multiple threads (using a single JVM). However, in my situation I need them to run forked in different JMVs per suite XML file. While there are also fork options, they don't seem to work icw suite XML files. So, what I want is that tests are execute sequentually in each forked JVM. So for example, JVM1 will work on all tests contained by suite XML 1 (running them sequentially). Then in parallel, JVM2,3,4 etc will do the same thing for tests contained in there assigned suite XML file. > Running suites forked > - > > Key: SUREFIRE-1237 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1237 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 >Reporter: Koen Serneels > > I have a Maven module in which I grouped test classes based on their package > into different TestNG suite files. The different suite's are listed in the > plugin config using . The tests identified by the suites are > ran sequentially ootb by surefire. With the current version it is already > possible to run the tests within the suites in parallel using multiple > threads (within a single JVM). > However, in my situation I need them to run forked in different JMVs. So what > I want is a JVM fork per suite XML file and not multiple threads. While > there are also fork options, they don't seem to work in combination with > suite XML files (but rather with methods and or test classes). > So, what I'm after is an option that creates a pool of forked JVM's which > takes care of running the available suite XML files. For ex. > "suites 8". Each fork will then execute it's > test (as identified by the suite XML file) in sequence. So for example, in > the config given above, there will be 8 forked JVM's. When I have 10 suite > XML files, each JVM will start working on the tests identified by its > assigned suite XML. So, JVM1 will run all tests (sequentially) identified by > suite XML1. In parallel, JVM2-8 will do the same thing for their assigned > suite XML. From the moment a forked JVM is done processing its suite XML file > it will start on the next one until they are all processed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SUREFIRE-1237) Running suites forked
[ https://issues.apache.org/jira/browse/SUREFIRE-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koen Serneels updated SUREFIRE-1237: Description: At the moment I grouped the test classes of a Maven module into different TestNG suite files based on some criteria. The different suite's are ran sequentially ootb by surefire. With the current version it is possible to run the suites in parallel using multiple threads (using a single JVM). However, in my situation I need them to run forked in different JMVs per suite XML file. While there are also fork options, they don't seem to work icw suite XML files. So, what I want is that tests are execute sequentually in each forked JVM. So for example, JVM1 will work on all tests contained by suite XML 1 (running them sequentially). Then in parallel, JVM2,3,4 etc will do the same thing for tests contained in there assigned suite XML file. was:At the moment I grouped the test classes of a Maven module into different TestNG suite files based on some criteria. The different suite's are ran sequentially ootb by surefire. With the current version it is possible to run the suites in parallel using multiple threads. However, in my situation I need them to run forked in different JMVs per suite XML file. The tests in each JVM are then executed sequentially. So for example, JVM1 will work on all tests contained by suite1 (running them sequentially) in parallel, JVM2,3,4 etc will do the same thing for their assigned suite XML file. > Running suites forked > - > > Key: SUREFIRE-1237 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1237 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 >Reporter: Koen Serneels > > At the moment I grouped the test classes of a Maven module into different > TestNG suite files based on some criteria. The different suite's are ran > sequentially ootb by surefire. With the current version it is possible to run > the suites in parallel using multiple threads (using a single JVM). > However, in my situation I need them to run forked in different JMVs per > suite XML file. While there are also fork options, they don't seem to work > icw suite XML files. So, what I want is that tests are execute sequentually > in each forked JVM. So for example, JVM1 will work on all tests contained by > suite XML 1 (running them sequentially). Then in parallel, JVM2,3,4 etc will > do the same thing for tests contained in there assigned suite XML file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SUREFIRE-1237) Running suites forked
[ https://issues.apache.org/jira/browse/SUREFIRE-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koen Serneels updated SUREFIRE-1237: Description: At the moment I grouped the test classes of a Maven module into different TestNG suite files based on some criteria. The different suite's are ran sequentially ootb by surefire. With the current version it is possible to run the suites in parallel using multiple threads. However, in my situation I need them to run forked in different JMVs per suite XML file. The tests in each JVM are then executed sequentially. So for example, JVM1 will work on all tests contained by suite1 (running them sequentially) in parallel, JVM2,3,4 etc will do the same thing for their assigned suite XML file. (was: At the moment I grouped the test classes of a Maven module into different TestNG suite files based on some criteria. The different suite's are ran sequentially ootb by surefire. With the current version it is possible to run the suites in parallel using multiple threads. However, in my situation I need them to run forked in different JMVs per suite XML file. In each JVM the tests then sequentially. So for example, JVM1 will work on all tests contained by suite1 (running them sequentially) in parallel, JVM2,3,4 etc will do the same thing for their assigned suite XML file.) > Running suites forked > - > > Key: SUREFIRE-1237 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1237 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 >Reporter: Koen Serneels > > At the moment I grouped the test classes of a Maven module into different > TestNG suite files based on some criteria. The different suite's are ran > sequentially ootb by surefire. With the current version it is possible to run > the suites in parallel using multiple threads. However, in my situation I > need them to run forked in different JMVs per suite XML file. The tests in > each JVM are then executed sequentially. So for example, JVM1 will work on > all tests contained by suite1 (running them sequentially) in parallel, > JVM2,3,4 etc will do the same thing for their assigned suite XML file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SUREFIRE-1237) Running suites forked
[ https://issues.apache.org/jira/browse/SUREFIRE-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koen Serneels updated SUREFIRE-1237: Description: At the moment I grouped the test classes of a Maven module into different TestNG suite files based on some criteria. The different suite's are ran sequentially ootb by surefire. With the current version it is possible to run the suites in parallel using multiple threads. However, in my situation I need them to run forked in different JMVs per suite XML file. In each JVM the tests then sequentially. So for example, JVM1 will work on all tests contained by suite1 (running them sequentially) in parallel, JVM2,3,4 etc will do the same thing for their assigned suite XML file. (was: At the moment I grouped the test classes of a Maven module into different TestNG suite files based on some criteria. The different suite's are ran sequentially ootb by surefire. With the current version it is possible to run the suites in parallel using multiple threads. However, in my situation In need different JMVs per suite XML file, in which each test need to run sequentially. So for example, JVM1 will work on all tests contained by suite1 (running them sequentially) but in the meantime JVM2,3,4 etc will do the same thing for their suite XML file.) > Running suites forked > - > > Key: SUREFIRE-1237 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1237 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Surefire Plugin >Affects Versions: 2.19.1 >Reporter: Koen Serneels > > At the moment I grouped the test classes of a Maven module into different > TestNG suite files based on some criteria. The different suite's are ran > sequentially ootb by surefire. With the current version it is possible to run > the suites in parallel using multiple threads. However, in my situation I > need them to run forked in different JMVs per suite XML file. In each JVM the > tests then sequentially. So for example, JVM1 will work on all tests > contained by suite1 (running them sequentially) in parallel, JVM2,3,4 etc > will do the same thing for their assigned suite XML file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SUREFIRE-1237) Running suites forked
Koen Serneels created SUREFIRE-1237: --- Summary: Running suites forked Key: SUREFIRE-1237 URL: https://issues.apache.org/jira/browse/SUREFIRE-1237 Project: Maven Surefire Issue Type: New Feature Components: Maven Surefire Plugin Affects Versions: 2.19.1 Reporter: Koen Serneels At the moment I grouped the test classes of a Maven module into different TestNG suite files based on some criteria. The different suite's are ran sequentially ootb by surefire. With the current version it is possible to run the suites in parallel using multiple threads. However, in my situation In need different JMVs per suite XML file, in which each test need to run sequentially. So for example, JVM1 will work on all tests contained by suite1 (running them sequentially) but in the meantime JVM2,3,4 etc will do the same thing for their suite XML file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] (MRELEASE-812) "prepare" does not commit before tagging and therefore deploys snapshot instead of release
[
https://jira.codehaus.org/browse/MRELEASE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=351340#comment-351340
]
Koen Serneels edited comment on MRELEASE-812 at 8/12/14 3:10 PM:
-
I was experiencing the same issue (Git 1.9.1/Ubuntu). The release plugin (was
using 2.4.2) would not commit anymore, resulting in the SNAPSHOT suffix being
present in the tag.
Bumping the release plugin to 2.5 solved the problem for projects having the
pom.xml in the repository root.
However, I had another project with the pom.xml NOT directly in the repository
root. For this bumping to 2.5 alone was not enough. To fix this the SCM api
and gitexe dependency also need to be overridden to the latest version (1.9.1
atm). This solved the problem there as well with the release plugin still at
v2.5
{code}
org.apache.maven.scm
maven-scm-api
1.9.1
org.apache.maven.scm
maven-scm-provider-gitexe
1.9.1
{code}
See also https://jira.codehaus.org/browse/SCM-740
was (Author: koen.serneels):
I was experiencing the same issue (Git 1.9.1/Ubuntu). The release plugin (still
using 2.4.2) would not commit, resulting in the SNAPSHOT suffix being present
in the tag.
Bumping the release plugin to 2.5 solved the problem for projects having the
pom.xml in the repository root.
However, I had another project with the pom.xml NOT directly in the repository
root. For this overriding the SCM api and gitexe dependency to the latest
version (1.9.1 atm) solved the problem there as well (while still using the
latest release plugin version being 2.5 atm)
{code}
org.apache.maven.scm
maven-scm-api
1.9.1
org.apache.maven.scm
maven-scm-provider-gitexe
1.9.1
{code}
See also https://jira.codehaus.org/browse/SCM-740
> "prepare" does not commit before tagging and therefore deploys snapshot
> instead of release
> --
>
> Key: MRELEASE-812
> URL: https://jira.codehaus.org/browse/MRELEASE-812
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: Git
>Affects Versions: 2.3.2, 2.4
>Reporter: Andrei Pozolotin
>Assignee: Robert Scholte
>Priority: Critical
> Fix For: 2.5
>
> Attachments: mvn-2.3.2.txt, mvn-2.4.0.txt
>
>
> thank you very much for new release!
> http://mail-archives.apache.org/mod_mbox/maven-announce/201212.mbox/%3Cop.wpjbptp1kdkhrr@columbia%3E
> it seems we need an emergency fix:
> attached are 2 logs:
> 1) mvn-2.3.2.txt invocation that works fine with 2.3.2
> 2) mvn-2.4.0.txt invocation that fails with 2.4
> problem:
> "perform" does not commit tags, deploys snapshot instead of release
> here is project parent:
> http://search.maven.org/remotecontent?filepath=com/barchart/base/barchart-archon/2.3.6/barchart-archon-2.3.6.pom
> build is invoked both times with this:
> mvn --define resume=false release:prepare
> mvn --define resume=false release:perform
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MRELEASE-812) "prepare" does not commit before tagging and therefore deploys snapshot instead of release
[
https://jira.codehaus.org/browse/MRELEASE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=351340#comment-351340
]
Koen Serneels edited comment on MRELEASE-812 at 8/12/14 3:06 PM:
-
I was experiencing the same issue (Git 1.9.1/Ubuntu). The release plugin (still
using 2.4.2) would not commit, resulting in the SNAPSHOT suffix being present
in the tag.
Bumping the release plugin to 2.5 solved the problem for projects having the
pom.xml in the repository root.
However, I had another project with the pom.xml NOT directly in the repository
root. For this overriding the SCM api and gitexe dependency to the latest
version (1.9.1 atm) solved the problem there as well (while still using the
latest release plugin version being 2.5 atm)
{code}
org.apache.maven.scm
maven-scm-api
1.9.1
org.apache.maven.scm
maven-scm-provider-gitexe
1.9.1
{code}
See also https://jira.codehaus.org/browse/SCM-740
was (Author: koen.serneels):
I was experiencing the same issue (Git 1.9.1/Ubuntu). The release plugin (still
using 2.4.2) would not commit, resulting in the SNAPSHOT suffix being present
in the tag.
Bumping the release plugin to 2.5 solved the problem for projects having the
pom.xml in the repository root.
However, I had another project with the pom.xml NOT directly in the repository
root. For this overriding the SCM api and gitexe dependency to the latest
version (1.9.1 atm) solved the problem there as well (while still using the
latest release plugin version being 2.5 atm)
[code]
org.apache.maven.scm
maven-scm-api
1.9.1
org.apache.maven.scm
maven-scm-provider-gitexe
1.9.1
[/code]
See also https://jira.codehaus.org/browse/SCM-740
> "prepare" does not commit before tagging and therefore deploys snapshot
> instead of release
> --
>
> Key: MRELEASE-812
> URL: https://jira.codehaus.org/browse/MRELEASE-812
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: Git
>Affects Versions: 2.3.2, 2.4
>Reporter: Andrei Pozolotin
>Assignee: Robert Scholte
>Priority: Critical
> Fix For: 2.5
>
> Attachments: mvn-2.3.2.txt, mvn-2.4.0.txt
>
>
> thank you very much for new release!
> http://mail-archives.apache.org/mod_mbox/maven-announce/201212.mbox/%3Cop.wpjbptp1kdkhrr@columbia%3E
> it seems we need an emergency fix:
> attached are 2 logs:
> 1) mvn-2.3.2.txt invocation that works fine with 2.3.2
> 2) mvn-2.4.0.txt invocation that fails with 2.4
> problem:
> "perform" does not commit tags, deploys snapshot instead of release
> here is project parent:
> http://search.maven.org/remotecontent?filepath=com/barchart/base/barchart-archon/2.3.6/barchart-archon-2.3.6.pom
> build is invoked both times with this:
> mvn --define resume=false release:prepare
> mvn --define resume=false release:perform
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MRELEASE-812) "prepare" does not commit before tagging and therefore deploys snapshot instead of release
[ https://jira.codehaus.org/browse/MRELEASE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=351340#comment-351340 ] Koen Serneels commented on MRELEASE-812: I was experiencing the same issue (Git 1.9.1/Ubuntu). The release plugin (still using 2.4.2) would not commit, resulting in the SNAPSHOT suffix being present in the tag. Bumping the release plugin to 2.5 solved the problem for projects having the pom.xml in the repository root. However, I had another project with the pom.xml NOT directly in the repository root. For this overriding the SCM api and gitexe dependency to the latest version (1.9.1 atm) solved the problem there as well (while still using the latest release plugin version being 2.5 atm) [code] org.apache.maven.scm maven-scm-api 1.9.1 org.apache.maven.scm maven-scm-provider-gitexe 1.9.1 [/code] See also https://jira.codehaus.org/browse/SCM-740 > "prepare" does not commit before tagging and therefore deploys snapshot > instead of release > -- > > Key: MRELEASE-812 > URL: https://jira.codehaus.org/browse/MRELEASE-812 > Project: Maven Release Plugin > Issue Type: Bug > Components: Git >Affects Versions: 2.3.2, 2.4 >Reporter: Andrei Pozolotin >Assignee: Robert Scholte >Priority: Critical > Fix For: 2.5 > > Attachments: mvn-2.3.2.txt, mvn-2.4.0.txt > > > thank you very much for new release! > http://mail-archives.apache.org/mod_mbox/maven-announce/201212.mbox/%3Cop.wpjbptp1kdkhrr@columbia%3E > it seems we need an emergency fix: > attached are 2 logs: > 1) mvn-2.3.2.txt invocation that works fine with 2.3.2 > 2) mvn-2.4.0.txt invocation that fails with 2.4 > problem: > "perform" does not commit tags, deploys snapshot instead of release > here is project parent: > http://search.maven.org/remotecontent?filepath=com/barchart/base/barchart-archon/2.3.6/barchart-archon-2.3.6.pom > build is invoked both times with this: > mvn --define resume=false release:prepare > mvn --define resume=false release:perform -- This message was sent by Atlassian JIRA (v6.1.6#6162)
