[jira] [Commented] (SUREFIRE-1302) Surefire does not wait long enough for the forked VM and assumes it to be dead
[
https://issues.apache.org/jira/browse/SUREFIRE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15701283#comment-15701283
]
Yuriy Zaplavnov commented on SUREFIRE-1302:
---
Sorry for delay, was a bit in hurry with other things, give me please some time
and I will take it to prepare a project to let you reproduce it on your own.
> Surefire does not wait long enough for the forked VM and assumes it to be dead
> --
>
> Key: SUREFIRE-1302
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1302
> Project: Maven Surefire
> Issue Type: Request
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Yuriy Zaplavnov
>Assignee: Tibor Digana
> Fix For: Backlog
>
> Attachments: tests_log_01.txt, tests_log_02.txt
>
>
> This issue happens because surefire kills the forked container if it times
> out waiting for the 'ping'.
> In org.apache.maven.surefire.booter.ForkedBooter class there is hardcoded
> constant PING_TIMEOUT_IN_SECONDS = 20 which is used in the following method:
> {code}
> private static ScheduledFuture listenToShutdownCommands( CommandReader
> reader )
> {
> reader.addShutdownListener( createExitHandler( reader ) );
> AtomicBoolean pingDone = new AtomicBoolean( true );
> reader.addNoopListener( createPingHandler( pingDone ) );
> return JVM_TERMINATOR.scheduleAtFixedRate( createPingJob( pingDone,
> reader ),
>0,PING_TIMEOUT_IN_SECONDS,
> SECONDS );
> }
> {code}
> to create ScheduledFuture.
> In some of the cases the forked container might respond a bit later than it's
> expected and surefire kills it
> {code}
> private static Runnable createPingJob( final AtomicBoolean pingDone, final
> CommandReader reader )
> {
> return new Runnable()
> {
> public void run()
> {
> boolean hasPing = pingDone.getAndSet( false );
> if ( !hasPing )
> {
> exit( 1, KILL, reader, true );
> }
> }
> };
> }
> {code}
> As long as we need to terminate it anyway, It would be really helpful if the
> problem could be solved making the PING_TIMEOUT_IN_SECONDS configurable with
> the ability to specify the value from maven-surefire-plugin.
> It would help to configure this timeout based on needs and factors of the
> projects where surefire runs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (WAGON-468) settings.xml server httpConfiguration ignored
[
https://issues.apache.org/jira/browse/WAGON-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakub Bochenski updated WAGON-468:
--
Description:
Since Jenkins requires preemptive authentication I've configured {{httpClient}}
provder in {{settings.xml}} to provide it.
This works fine with "usual" maven artifact resolution, as well as with
{{dependency:get}} etc.
{code}http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.1.0
http://maven.apache.org/xsd/settings-1.1.0.xsd";>
http://maven.apache.org/SETTINGS/1.1.0";>/home/jbochenski/.m2/repository
http://maven.apache.org/SETTINGS/1.1.0";>
jbochenski
***
httpclient
true
jenkins
http://maven.apache.org/SETTINGS/1.1.0";>
org.apache.maven.plugins
org.codehaus.mojo
{code}
However {{wagon:list}} fails with {{Failed to execute goal
org.codehaus.mojo:wagon-maven-plugin:1.0:list (default-cli) on project
standalone-pom: Error handling resource: Access denied to: }}
{code}ClassRealm[plugin>org.codehaus.mojo:wagon-maven-plugin:1.0, parent:
sun.misc.Launcher$AppClassLoader@55f96302]
[DEBUG] Configuring mojo 'org.codehaus.mojo:wagon-maven-plugin:1.0:list' with
basic configurator -->
[DEBUG] (f) caseSensitive = true
[DEBUG] (f) includes = *
[DEBUG] (f) project = MavenProject: org.apache.maven:standalone-pom:1 @
[DEBUG] (f) serverId = jenkins
[DEBUG] (f) settings = org.apache.maven.execution.SettingsAdapter@5215cd9a
[DEBUG] (f) skip = false
{code}
was:
Since Jenkins requires preemptive authentication I've configured{{httpClient}}
provder in {{settings.xml}} to provide it.
This works fine with "usual" maven artifact resolution, as well as with
{{dependency:get}} etc.
{code}http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.1.0
http://maven.apache.org/xsd/settings-1.1.0.xsd";>
http://maven.apache.org/SETTINGS/1.1.0";>/home/jbochenski/.m2/repository
http://maven.apache.org/SETTINGS/1.1.0";>
jbochenski
***
httpclient
true
jenkins
http://maven.apache.org/SETTINGS/1.1.0";>
org.apache.maven.plugins
org.codehaus.mojo
{code}
However {{wagon:list}} fails with {{Failed to execute goal
org.codehaus.mojo:wagon-maven-plugin:1.0:list (default-cli) on project
standalone-pom: Error handling resource: Access denied to: }}
{code}ClassRealm[plugin>org.codehaus.mojo:wagon-maven-plugin:1.0, parent:
sun.misc.Launcher$AppClassLoader@55f96302]
[DEBUG] Configuring mojo 'org.codehaus.mojo:wagon-maven-plugin:1.0:list' with
basic configurator -->
[DEBUG] (f) caseSensitive = true
[DEBUG] (f) includes = *
[DEBUG] (f) project = MavenProject: org.apache.maven:standalone-pom:1 @
[DEBUG] (f) serverId = jenkins
[DEBUG] (f) settings = org.apache.maven.execution.SettingsAdapter@5215cd9a
[DEBUG] (f) skip = false
{code}
> settings.xml server httpConfiguration ignored
> -
>
> Key: WAGON-468
> URL: https://issues.apache.org/jira/browse/WAGON-468
> Project: Maven Wagon
> Issue Type: Bug
>Affects Versions: 1.0
>Reporter: Jakub Bochenski
>Assignee: Dan Tran
>Priority: Blocker
>
> Since Jenkins requires preemptive authentication I've configured
> {{httpClient}} provder in {{settings.xml}} to provide it.
> This works fine with "usual" maven artifact resolution, as well as with
> {{dependency:get}} etc.
> {code}http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.1.0
> http://maven.apache.org/xsd/settings-1.1.0.xsd";>
>xmlns="http://maven.apache.org/SETTINGS/1.1.0";>/home/jbochenski/.m2/repository
> http://maven.apache.org/SETTINGS/1.1.0";>
>
> jbochenski
> ***
>
> httpclient
>
>
> true
>
>
>
> jenkins
>
>
> http://maven.apache.org/SETTINGS/1.1.0";>
> org.apache.maven.plugins
> org.codehaus.mojo
>
>
> {code}
> However {{wagon:list}} fails with {{Failed to execute goal
> org.codehaus.mojo:wagon-maven-plugin:1.0:list (default-cli) on project
> standalone-pom: Error handling resource: Access denied to: }}
> {code}ClassRealm[plugin>org.codehaus.mojo:wagon-maven-plugin:1.0, parent:
> sun.misc.Launcher$AppClassLoader@55f96302]
> [DEBUG] Configuring mojo 'org.codehaus.mojo:wagon-maven-plugin:1.0:list' with
> basic configurator -->
> [DEBUG] (f) caseSensitive = true
> [DEBUG] (f) includes = *
> [DEBUG] (f)
[jira] [Closed] (MCHECKSTYLE-321) Be able to check root files
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Zurczak closed MCHECKSTYLE-321. --- Resolution: Workaround > Be able to check root files > --- > > Key: MCHECKSTYLE-321 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-321 > Project: Maven Checkstyle Plugin > Issue Type: Improvement > Components: checkstyle:check >Affects Versions: 2.17 >Reporter: Vincent Zurczak >Priority: Trivial > > Today, the Maven Checkstyle plug-in allows to verify files within the Maven > directories: sources, test sources, resources and test resources. > In addition to this, I would personnaly like to verify my *pom.xml* file. > I have tried many things but I did not succeed in validating my POM files > with Checkstyle. And looking at the code, I think I saw why. > The reason for such a verification is that this file also contains license > headers that I would like to keep verified. And I am pretty sure there would > be other rules I would like to check (such as indentation, etc). > If we consider other project kinds, such as Eclipse plug-ins, one may want to > verify *plugin.xml* and *feature.xml* files. So, it would be nice to be able > to specify *otherIncludes* in the plug-in's configuration. This new parameter > would contain a list of files to verify, when they exist. > If the idea is accepted, I am ready to contribute a patch for this feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCHECKSTYLE-321) Be able to check root files
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15702822#comment-15702822 ] Vincent Zurczak commented on MCHECKSTYLE-321: - Thanks Noémi for the workaround. :) It indeed works well. I will close the issue then. > Be able to check root files > --- > > Key: MCHECKSTYLE-321 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-321 > Project: Maven Checkstyle Plugin > Issue Type: Improvement > Components: checkstyle:check >Affects Versions: 2.17 >Reporter: Vincent Zurczak >Priority: Trivial > > Today, the Maven Checkstyle plug-in allows to verify files within the Maven > directories: sources, test sources, resources and test resources. > In addition to this, I would personnaly like to verify my *pom.xml* file. > I have tried many things but I did not succeed in validating my POM files > with Checkstyle. And looking at the code, I think I saw why. > The reason for such a verification is that this file also contains license > headers that I would like to keep verified. And I am pretty sure there would > be other rules I would like to check (such as indentation, etc). > If we consider other project kinds, such as Eclipse plug-ins, one may want to > verify *plugin.xml* and *feature.xml* files. So, it would be nice to be able > to specify *otherIncludes* in the plug-in's configuration. This new parameter > would contain a list of files to verify, when they exist. > If the idea is accepted, I am ready to contribute a patch for this feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MRELEASE-968) Maven release plugin missing dependency
[
https://issues.apache.org/jira/browse/MRELEASE-968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15703236#comment-15703236
]
Farid Zakaria commented on MRELEASE-968:
sorry for late reply due to thanksigiving.
{noformat}
casper-common git:(object-metadata-verifier) ✗ ll
/usr/local/Cellar/maven/3.3.9/libexec/lib/plexus-cipher-1.7.jar
-rw-r--r-- 1 fmzakari admin13K May 7 2013
/usr/local/Cellar/maven/3.3.9/libexec/lib/plexus-cipher-1.7.jar
casper-common git:(object-metadata-verifier) ✗ jar -tf
/usr/local/Cellar/maven/3.3.9/libexec/lib/plexus-cipher-1.7.jar
META-INF/
META-INF/MANIFEST.MF
META-INF/sisu/
META-INF/plexus/
org/
org/sonatype/
org/sonatype/plexus/
org/sonatype/plexus/components/
org/sonatype/plexus/components/cipher/
META-INF/sisu/javax.inject.Named
META-INF/plexus/components.xml
org/sonatype/plexus/components/cipher/PlexusCipherException.class
org/sonatype/plexus/components/cipher/Base64.class
org/sonatype/plexus/components/cipher/PlexusCipher.class
org/sonatype/plexus/components/cipher/DefaultPlexusCipher.class
org/sonatype/plexus/components/cipher/PBECipher.class
META-INF/maven/
META-INF/maven/org.sonatype.plexus/
META-INF/maven/org.sonatype.plexus/plexus-cipher/
META-INF/maven/org.sonatype.plexus/plexus-cipher/pom.xml
META-INF/maven/org.sonatype.plexus/plexus-cipher/pom.properties
{noformat}
> Maven release plugin missing dependency
> ---
>
> Key: MRELEASE-968
> URL: https://issues.apache.org/jira/browse/MRELEASE-968
> Project: Maven Release Plugin
> Issue Type: Bug
>Affects Versions: 2.5.3
>Reporter: Farid Zakaria
> Fix For: 3.0.0
>
>
> I've encountered the following error when trying to perform a maven-release
> prepare goal
> {noformat}
> mvn -DdryRun=true org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO]
>
> [INFO] Building 1.2.2-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-release-plugin:2.5.3:prepare (default-cli) @ X ---
> [WARNING] Error injecting:
> org.sonatype.plexus.components.sec.dispatcher.DefaultSecDispatcher
> java.lang.NoClassDefFoundError:
> org/sonatype/plexus/components/cipher/PlexusCipherException
> at java.lang.Class.getDeclaredConstructors0(Native Method)
> at java.lang.Class.privateGetDeclaredConstructors(Class.java:2671)
> at java.lang.Class.getDeclaredConstructors(Class.java:2020)
> at
> com.google.inject.spi.InjectionPoint.forConstructorOf(InjectionPoint.java:245)
> at
> com.google.inject.internal.ConstructorBindingImpl.create(ConstructorBindingImpl.java:99)
> at
> com.google.inject.internal.InjectorImpl.createUninitializedBinding(InjectorImpl.java:658)
> at
> com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorImpl.java:882)
> at
> com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(InjectorImpl.java:805)
> at
> com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl.java:282)
> at
> com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImpl.java:214)
> at
> com.google.inject.internal.InjectorImpl.getProviderOrThrow(InjectorImpl.java:1006)
> at
> com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1038)
> at
> com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1001)
> at
> com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1051)
> at
> org.eclipse.sisu.space.AbstractDeferredClass.get(AbstractDeferredClass.java:48)
> at
> com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:81)
> at
> com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:53)
> at
> com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:65)
> at
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:115)
> at
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:133)
> at
> com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:68)
> at
> com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:63)
> at
> com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:45)
> at
> com.google.inject.internal.Provid
[jira] [Comment Edited] (MRELEASE-968) Maven release plugin missing dependency
[
https://issues.apache.org/jira/browse/MRELEASE-968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15703236#comment-15703236
]
Farid Zakaria edited comment on MRELEASE-968 at 11/28/16 9:46 PM:
--
sorry for late reply due to thanksigiving.
{noformat}
$ ll /usr/local/Cellar/maven/3.3.9/libexec/lib/plexus-cipher-1.7.jar
-rw-r--r-- 1 fmzakari admin13K May 7 2013
/usr/local/Cellar/maven/3.3.9/libexec/lib/plexus-cipher-1.7.jar
$ jar -tf /usr/local/Cellar/maven/3.3.9/libexec/lib/plexus-cipher-1.7.jar
META-INF/
META-INF/MANIFEST.MF
META-INF/sisu/
META-INF/plexus/
org/
org/sonatype/
org/sonatype/plexus/
org/sonatype/plexus/components/
org/sonatype/plexus/components/cipher/
META-INF/sisu/javax.inject.Named
META-INF/plexus/components.xml
org/sonatype/plexus/components/cipher/PlexusCipherException.class
org/sonatype/plexus/components/cipher/Base64.class
org/sonatype/plexus/components/cipher/PlexusCipher.class
org/sonatype/plexus/components/cipher/DefaultPlexusCipher.class
org/sonatype/plexus/components/cipher/PBECipher.class
META-INF/maven/
META-INF/maven/org.sonatype.plexus/
META-INF/maven/org.sonatype.plexus/plexus-cipher/
META-INF/maven/org.sonatype.plexus/plexus-cipher/pom.xml
META-INF/maven/org.sonatype.plexus/plexus-cipher/pom.properties
{noformat}
was (Author: fmzakari):
sorry for late reply due to thanksigiving.
{noformat}
casper-common git:(object-metadata-verifier) ✗ ll
/usr/local/Cellar/maven/3.3.9/libexec/lib/plexus-cipher-1.7.jar
-rw-r--r-- 1 fmzakari admin13K May 7 2013
/usr/local/Cellar/maven/3.3.9/libexec/lib/plexus-cipher-1.7.jar
casper-common git:(object-metadata-verifier) ✗ jar -tf
/usr/local/Cellar/maven/3.3.9/libexec/lib/plexus-cipher-1.7.jar
META-INF/
META-INF/MANIFEST.MF
META-INF/sisu/
META-INF/plexus/
org/
org/sonatype/
org/sonatype/plexus/
org/sonatype/plexus/components/
org/sonatype/plexus/components/cipher/
META-INF/sisu/javax.inject.Named
META-INF/plexus/components.xml
org/sonatype/plexus/components/cipher/PlexusCipherException.class
org/sonatype/plexus/components/cipher/Base64.class
org/sonatype/plexus/components/cipher/PlexusCipher.class
org/sonatype/plexus/components/cipher/DefaultPlexusCipher.class
org/sonatype/plexus/components/cipher/PBECipher.class
META-INF/maven/
META-INF/maven/org.sonatype.plexus/
META-INF/maven/org.sonatype.plexus/plexus-cipher/
META-INF/maven/org.sonatype.plexus/plexus-cipher/pom.xml
META-INF/maven/org.sonatype.plexus/plexus-cipher/pom.properties
{noformat}
> Maven release plugin missing dependency
> ---
>
> Key: MRELEASE-968
> URL: https://issues.apache.org/jira/browse/MRELEASE-968
> Project: Maven Release Plugin
> Issue Type: Bug
>Affects Versions: 2.5.3
>Reporter: Farid Zakaria
> Fix For: 3.0.0
>
>
> I've encountered the following error when trying to perform a maven-release
> prepare goal
> {noformat}
> mvn -DdryRun=true org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO]
>
> [INFO] Building 1.2.2-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-release-plugin:2.5.3:prepare (default-cli) @ X ---
> [WARNING] Error injecting:
> org.sonatype.plexus.components.sec.dispatcher.DefaultSecDispatcher
> java.lang.NoClassDefFoundError:
> org/sonatype/plexus/components/cipher/PlexusCipherException
> at java.lang.Class.getDeclaredConstructors0(Native Method)
> at java.lang.Class.privateGetDeclaredConstructors(Class.java:2671)
> at java.lang.Class.getDeclaredConstructors(Class.java:2020)
> at
> com.google.inject.spi.InjectionPoint.forConstructorOf(InjectionPoint.java:245)
> at
> com.google.inject.internal.ConstructorBindingImpl.create(ConstructorBindingImpl.java:99)
> at
> com.google.inject.internal.InjectorImpl.createUninitializedBinding(InjectorImpl.java:658)
> at
> com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorImpl.java:882)
> at
> com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(InjectorImpl.java:805)
> at
> com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl.java:282)
> at
> com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImpl.java:214)
> at
> com.google.inject.internal.InjectorImpl.getProviderOrThrow(InjectorImpl.java:1006)
> at
> com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1038)
> at
> com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1001)
> at
> com.google.inject.internal.InjectorImpl.
[jira] [Created] (MRELEASE-969) Ability to specify tag for release:perform
Gili created MRELEASE-969: - Summary: Ability to specify tag for release:perform Key: MRELEASE-969 URL: https://issues.apache.org/jira/browse/MRELEASE-969 Project: Maven Release Plugin Issue Type: Improvement Reporter: Gili (This issue was reported in the past but it looks like got lost in the migration from codehaus.org to apache.org) We need a way to specify a tag either to release:perform or the HG scm provider. http://maven.apache.org/maven-release/maven-release-plugin/examples/perform-release.html indicates that we should be able to release:perform from a tag without the use of release.properties but there is no way to specify a tag for the HG scm provider. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1295) JVM crashes in forks do not log the name of the failing test
[
https://issues.apache.org/jira/browse/SUREFIRE-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15703338#comment-15703338
]
ASF GitHub Bot commented on SUREFIRE-1295:
--
GitHub user Tibor17 opened a pull request:
https://github.com/apache/maven-surefire/pull/136
[SUREFIRE-1295] Attribute JVM crashes to tests
I have 4 tests ATest.java .. DTest.java, and CTest fails like this:
```
@Test
public void x() {
Runtime.getRuntime().halt( 0 );
}
```
Here is the result, see "Crashed tests".
```
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.19.2-SNAPSHOT:test
(default-test) on project b: Execution default-test of goal
org.apache.maven.plugins:maven-surefire-plugin:2.19.2-SNAPSHOT:test failed: The
forked VM terminated without properly saying goodbye. VM crash or System.exit
called?
[ERROR] Command was cmd.exe /X /C ""D:\Program
Files\Java\jdk1.8.0_112\jre\bin\java" -jar
D:\vcs\zmaz6\target\surefire\surefirebooter8109843199172464014.jar
D:\vcs\zmaz6\target\surefire\surefire4550764212193522341tmp
D:\vcs\zmaz6\target\surefire\surefire_07316673656092271862tmp"
[ERROR] Process Exit Code: 0
[ERROR] Crashed tests:
[ERROR] pkg.CTest
[ERROR] -> [Help 1]
```
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Tibor17/maven-surefire SUREFIRE-1295
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/maven-surefire/pull/136.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #136
commit 364b0c9e8ae56916f0b9aead2a26f07ed57befca
Author: Tibor17
Date: 2016-11-28T22:16:20Z
[SUREFIRE-1295] Attribute JVM crashes to tests
> JVM crashes in forks do not log the name of the failing test
>
>
> Key: SUREFIRE-1295
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1295
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Tandy
>Assignee: Tibor Digana
>
> I am using Surefire to test code accessed through JNI. Sometimes this code
> will fail, crashing the JVM.
> We run these tests in parallel ( forkCount=1C and reuseForks=false ) and it's
> not always obvious from the logs, which test caused a JVM crash - and
> although a command line is printed out, the booter temp files are removed
> automatically.
> For example:
> {code}
> [INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @
> crash-during-test ---
> ---
> T E S T S
> ---
> Running junit44.environment.BasicTest
> Results :
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.337 s
> [INFO] Finished at: 2016-10-26T21:56:45+01:00
> [INFO] Final Memory: 19M/451M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on
> project crash-during-test: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: The forked
> VM terminated without properly saying goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd
> /home/mtandy/Documents/surefire-vmcrash/maven-surefire/surefire-integration-tests/src/test/resources/crash-during-test
> && /usr/lib/jvm/java-8-oracle/jre/bin/java -jar
> /home/mtandy/Documents/surefire-vmcrash/maven-surefire/surefire-integration-tests/src/test/resources/crash-during-test/target/surefire/surefirebooter5241184363018251498.jar
>
> /home/mtandy/Documents/surefire-vmcrash/maven-surefire/surefire-integration-tests/src/test/resources/crash-during-test/target/surefire/surefire8973747106178765373tmp
>
> /home/mtandy/Documents/surefire-vmcrash/maven-surefire/surefire-integration-tests/src/test/resources/crash-during-test/target/surefire/surefire_01102526888161398167tmp
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> {co
[jira] [Commented] (SUREFIRE-1295) JVM crashes in forks do not log the name of the failing test
[
https://issues.apache.org/jira/browse/SUREFIRE-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15703343#comment-15703343
]
ASF GitHub Bot commented on SUREFIRE-1295:
--
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/130
@michaeltandy
I was inspired by your PR. Can you make a code review
https://github.com/apache/maven-surefire/pull/136?
I would like to run all IT tests and include yours.
> JVM crashes in forks do not log the name of the failing test
>
>
> Key: SUREFIRE-1295
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1295
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Tandy
>Assignee: Tibor Digana
>
> I am using Surefire to test code accessed through JNI. Sometimes this code
> will fail, crashing the JVM.
> We run these tests in parallel ( forkCount=1C and reuseForks=false ) and it's
> not always obvious from the logs, which test caused a JVM crash - and
> although a command line is printed out, the booter temp files are removed
> automatically.
> For example:
> {code}
> [INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @
> crash-during-test ---
> ---
> T E S T S
> ---
> Running junit44.environment.BasicTest
> Results :
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.337 s
> [INFO] Finished at: 2016-10-26T21:56:45+01:00
> [INFO] Final Memory: 19M/451M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on
> project crash-during-test: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: The forked
> VM terminated without properly saying goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd
> /home/mtandy/Documents/surefire-vmcrash/maven-surefire/surefire-integration-tests/src/test/resources/crash-during-test
> && /usr/lib/jvm/java-8-oracle/jre/bin/java -jar
> /home/mtandy/Documents/surefire-vmcrash/maven-surefire/surefire-integration-tests/src/test/resources/crash-during-test/target/surefire/surefirebooter5241184363018251498.jar
>
> /home/mtandy/Documents/surefire-vmcrash/maven-surefire/surefire-integration-tests/src/test/resources/crash-during-test/target/surefire/surefire8973747106178765373tmp
>
> /home/mtandy/Documents/surefire-vmcrash/maven-surefire/surefire-integration-tests/src/test/resources/crash-during-test/target/surefire/surefire_01102526888161398167tmp
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> {code}
> The situation could be improved if such crashes more closely resembled other
> test errors - such as by logging the test that was in progress when the crash
> happened.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MRELEASE-969) Ability to specify tag for release:perform
[ https://issues.apache.org/jira/browse/MRELEASE-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15703462#comment-15703462 ] Gili commented on MRELEASE-969: --- I found the original report at https://issues.apache.org/jira/browse/SCM-729 The comments suggest an easy fix (change the superclass). Can you please respond to let us know if this makes sense? > Ability to specify tag for release:perform > -- > > Key: MRELEASE-969 > URL: https://issues.apache.org/jira/browse/MRELEASE-969 > Project: Maven Release Plugin > Issue Type: Improvement >Reporter: Gili > > (This issue was reported in the past but it looks like got lost in the > migration from codehaus.org to apache.org) > We need a way to specify a tag either to release:perform or the HG scm > provider. > http://maven.apache.org/maven-release/maven-release-plugin/examples/perform-release.html > indicates that we should be able to release:perform from a tag without the > use of release.properties but there is no way to specify a tag for the HG scm > provider. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1295) JVM crashes in forks do not log the name of the failing test
[
https://issues.apache.org/jira/browse/SUREFIRE-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15703484#comment-15703484
]
ASF GitHub Bot commented on SUREFIRE-1295:
--
Github user michaeltandy commented on the issue:
https://github.com/apache/maven-surefire/pull/136
I've checked this against my integration test, and it looks OK to me.
My change reported which test method was running at the time of the crash,
rather than reporting only the class but for my application that doesn't matter
as most of our test classes contain a single test method.
If you want to merge my integration test into this, I pushed it to
https://github.com/michaeltandy/maven-surefire/tree/SUREFIRE-1295-tests-for-Tibor17
> JVM crashes in forks do not log the name of the failing test
>
>
> Key: SUREFIRE-1295
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1295
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Michael Tandy
>Assignee: Tibor Digana
>
> I am using Surefire to test code accessed through JNI. Sometimes this code
> will fail, crashing the JVM.
> We run these tests in parallel ( forkCount=1C and reuseForks=false ) and it's
> not always obvious from the logs, which test caused a JVM crash - and
> although a command line is printed out, the booter temp files are removed
> automatically.
> For example:
> {code}
> [INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @
> crash-during-test ---
> ---
> T E S T S
> ---
> Running junit44.environment.BasicTest
> Results :
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.337 s
> [INFO] Finished at: 2016-10-26T21:56:45+01:00
> [INFO] Final Memory: 19M/451M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on
> project crash-during-test: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: The forked
> VM terminated without properly saying goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd
> /home/mtandy/Documents/surefire-vmcrash/maven-surefire/surefire-integration-tests/src/test/resources/crash-during-test
> && /usr/lib/jvm/java-8-oracle/jre/bin/java -jar
> /home/mtandy/Documents/surefire-vmcrash/maven-surefire/surefire-integration-tests/src/test/resources/crash-during-test/target/surefire/surefirebooter5241184363018251498.jar
>
> /home/mtandy/Documents/surefire-vmcrash/maven-surefire/surefire-integration-tests/src/test/resources/crash-during-test/target/surefire/surefire8973747106178765373tmp
>
> /home/mtandy/Documents/surefire-vmcrash/maven-surefire/surefire-integration-tests/src/test/resources/crash-during-test/target/surefire/surefire_01102526888161398167tmp
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> {code}
> The situation could be improved if such crashes more closely resembled other
> test errors - such as by logging the test that was in progress when the crash
> happened.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (WAGON-468) settings.xml server httpConfiguration ignored
[
https://issues.apache.org/jira/browse/WAGON-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15703593#comment-15703593
]
Dan Tran commented on WAGON-468:
[~jbochenski] Could you give wagon-maven-plugin-1.1-SNAPSHOT to see it fixes
your reported issue
> settings.xml server httpConfiguration ignored
> -
>
> Key: WAGON-468
> URL: https://issues.apache.org/jira/browse/WAGON-468
> Project: Maven Wagon
> Issue Type: Bug
>Affects Versions: 1.0
>Reporter: Jakub Bochenski
>Assignee: Dan Tran
>Priority: Blocker
>
> Since Jenkins requires preemptive authentication I've configured
> {{httpClient}} provder in {{settings.xml}} to provide it.
> This works fine with "usual" maven artifact resolution, as well as with
> {{dependency:get}} etc.
> {code}http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.1.0
> http://maven.apache.org/xsd/settings-1.1.0.xsd";>
>xmlns="http://maven.apache.org/SETTINGS/1.1.0";>/home/jbochenski/.m2/repository
> http://maven.apache.org/SETTINGS/1.1.0";>
>
> jbochenski
> ***
>
> httpclient
>
>
> true
>
>
>
> jenkins
>
>
> http://maven.apache.org/SETTINGS/1.1.0";>
> org.apache.maven.plugins
> org.codehaus.mojo
>
>
> {code}
> However {{wagon:list}} fails with {{Failed to execute goal
> org.codehaus.mojo:wagon-maven-plugin:1.0:list (default-cli) on project
> standalone-pom: Error handling resource: Access denied to: }}
> {code}ClassRealm[plugin>org.codehaus.mojo:wagon-maven-plugin:1.0, parent:
> sun.misc.Launcher$AppClassLoader@55f96302]
> [DEBUG] Configuring mojo 'org.codehaus.mojo:wagon-maven-plugin:1.0:list' with
> basic configurator -->
> [DEBUG] (f) caseSensitive = true
> [DEBUG] (f) includes = *
> [DEBUG] (f) project = MavenProject: org.apache.maven:standalone-pom:1 @
> [DEBUG] (f) serverId = jenkins
> [DEBUG] (f) settings = org.apache.maven.execution.SettingsAdapter@5215cd9a
> [DEBUG] (f) skip = false
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MSITE-774) Usage of validate=true lead to "SAX2 driver class org.apache.xerces.parsers.SAXParser not found" exception
[
https://issues.apache.org/jira/browse/MSITE-774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15704281#comment-15704281
]
Roman Ivanov commented on MSITE-774:
issue is resolved in xml-maven-plugin project, will be released in version
after 1.0.1 .
> Usage of validate=true lead to "SAX2 driver class
> org.apache.xerces.parsers.SAXParser not found" exception
> --
>
> Key: MSITE-774
> URL: https://issues.apache.org/jira/browse/MSITE-774
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.5.1
>Reporter: Roman Ivanov
>Assignee: Hervé Boutemy
>
> project: https://github.com/checkstyle/checkstyle
> usage of validate=true:
> {code}
> ...
> org.apache.maven.plugins
> maven-site-plugin
> ${maven.site.plugin.version}
>
> ${basedir}/src/xdocs
> true
>
> ...
> {code}
> lead to
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.5.1:site (default-site) on
> project checkstyle: Error parsing
> '~/checkstyle/checkstyle/src/xdocs/anttask.xml.vm': line [-1] Error
> validating the model: SAX2 driver class org.apache.xerces.parsers.SAXParser
> not found -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.5.1:site (default-site) on
> project checkstyle: Error parsing
> '~/checkstyle/checkstyle/src/xdocs/anttask.xml.vm': line [-1] Error
> validating the model: SAX2 driver class org.apache.xerces.parsers.SAXParser
> not found
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error parsing
> '~/checkstyle/checkstyle/src/xdocs/anttask.xml.vm': line [-1] Error
> validating the model: SAX2 driver class org.apache.xerces.parsers.SAXParser
> not found
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:140)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 19 more
> Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error
> parsing '~/checkstyle/checkstyle/src/xdocs/anttask.xml.vm': line [-1] Error
> validating the model: SAX2 driver class org.apache.xerces.parsers.SAXParser
> not found
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:449)
> at
> org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:329)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderDoxiaDocuments(SiteMojo.java:264)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:171)
> at
> org.apache.maven.plugins.site.render.SiteM
