[JIRA] [testng] (JENKINS-12567) Skipped tests should not mark build as UNSTABLE
Patrik Johansson commented on JENKINS-12567 Skipped tests should not mark build as UNSTABLE I know this is coming in a bit late, but according to TestNG's documentation http://testng.org/doc/documentation-main.html it seems the default behaviour when test setup fails is to skip the suite. "Option Argument Documentation -configfailurepolicy skip|continue Whether TestNG should continue to execute the remaining tests in the suite or skip them if an @Before* method fails. Default behavior is skip." This might lead to some issues if the @Before method fails but Jenkins still doesn't set the job status to Unstable. Perhaps that config option would be a good idea? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testng] (JENKINS-12567) Skipped tests should not mark build as UNSTABLE
Patrik Johansson reopened JENKINS-12567 Skipped tests should not mark build as UNSTABLE I've added a late comment on this issue. Sorry for re-opening it. Change By: Patrik Johansson (24/May/13 7:48 AM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testng] (JENKINS-12567) Skipped tests should not mark build as UNSTABLE
Patrik Johansson edited a comment on JENKINS-12567 Skipped tests should not mark build as UNSTABLE I know this is coming in a bit late, but according to TestNG's documentation http://testng.org/doc/documentation-main.html it seems the default behaviour when test setup fails is to skip the suite. "Option Argument Documentation -configfailurepolicy skip|continue Whether TestNG should continue to execute the remaining tests in the suite or skip them if an @Before* method fails. Default behavior is skip." This might lead to some issues if the @Before method fails but Jenkins still doesn't set the job status to Unstable. Perhaps that config checkbox option would be a good idea? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [external-resource-dispatcher] (JENKINS-17469) The External Resources Manager should handle the state changes of the ExternalResource object
Patrik Johansson started work on JENKINS-17469 The External Resources Manager should handle the state changes of the ExternalResource object Change By: Patrik Johansson (04/Apr/13 12:25 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [external-resource-dispatcher] (JENKINS-17444) NoopExternalResourceManager fails to timeout reservations of resources on the master build node
Patrik Johansson created JENKINS-17444 NoopExternalResourceManager fails to timeout reservations of resources on the master build node Issue Type: Bug Affects Versions: current Assignee: rsandell Components: external-resource-dispatcher Created: 03/Apr/13 8:07 AM Description: The following error appears in the server log when I use the Noop manager and reserve resource 1234 on node "master" (the central Jenkins build node): WARNING: Failed to timeout a reservation of 1234 on node ! org.kohsuke.args4j.CmdLineException: No node with name exists on this Jenkins server. at com.sonyericsson.jenkins.plugins.externalresource.dispatcher.cli.ErCliUtils.findExternalResource(ErCliUtils.java:63) at com.sonyericsson.jenkins.plugins.externalresource.dispatcher.utils.resourcemanagers.NoopExternalResourceManager$ReservationTimeoutTask.run(NoopExternalResourceManager.ja va:113) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source) ←[0mapr 03, 2013 10:02:50 FM hudson.model.Run execute Environment: Windows 7, Jenkins 1.506, external-resource-dispatcher 1.0b Project: Jenkins Priority: Minor Reporter: Patrik Johansson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17269) 10 Testcases fail on Windows with error: hudson.util.IOException2: Failed to clean up temp dirs
Patrik Johansson created JENKINS-17269 10 Testcases fail on Windows with error: hudson.util.IOException2: Failed to clean up temp dirs Issue Type: Bug Assignee: rsandell Components: external-resource-dispatcher Created: 19/Mar/13 12:32 PM Description: Test results on windows Vista are: Package Tests Err Fail Skip Success Rate Time com.sonyericsson.jenkins.plugins.externalresource.dispatcher.utils.resourcemanagers 3 0 0 0 100% 5 com.sonyericsson.jenkins.plugins.externalresource.dispatcher.utils 4 1 1 0 50% 7 com.sonyericsson.jenkins.plugins.externalresource.dispatcher.spec 1 1 0 0 0% 4 com.sonyericsson.jenkins.plugins.externalresource.dispatcher.data 14 4 1 0 64.286% 76 com.sonyericsson.jenkins.plugins.externalresource.dispatcher8 4 0 0 50% 47 org.jvnet.hudson.test.junit1 0 0 0 100% 0 com.sonyericsson.jenkins.plugins.externalresource.dispatcher.cli 8 0 0 0 100% 10 org.jvnet.hudson.test 7 0 0 0 100% 0 10 tests fail with the following stack trace: hudson.util.IOException2: Failed to clean up temp dirs at org.jvnet.hudson.test.TemporaryDirectoryAllocator.dispose(TemporaryDirectoryAllocator.java:87) at org.jvnet.hudson.test.TestEnvironment.dispose(TestEnvironment.java:53) at org.jvnet.hudson.test.HudsonTestCase.tearDown(HudsonTestCase.java:352) at junit.framework.TestCase.runBare(TestCase.java:140) at org.jvnet.hudson.test.HudsonTestCase.runBare(HudsonTestCase.java:264) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:243) at junit.framework.TestSuite.run(TestSuite.java:238) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) at $Proxy0.invoke(Unknown Source) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) Caused by: java.io.IOException: Unable to delete C:\Users\xxx\AppData\Local\Temp\hudson2103820071219030666test\slave-slave0.log at hudson.Util.deleteFile(Util.java:266) at hudson.Util.deleteRecursive(Util.java:316) at hudson.Util.deleteContentsRecursive(Util.java:227) at hudson.Util.deleteRecursive(Util.java:307) at hudson.FilePath$9.invoke(FilePath.java:826) at hudson.FilePath$9.invoke(FilePath.java:824) at hudson.FilePath.act(FilePath.java:758) at hudson.FilePath.act(FilePath.java:740) at hudson.FilePath.deleteRecursive(FilePath.java:824) at org.jvnet.hudson.test.TemporaryDirectoryAllocator.dispose(TemporaryDirectoryAllocator.java:82) ... 23 more Environment: 1.0b, Win Vista Project: Jenkins Priority: Minor Reporter: Patrik Johansson
[JIRA] (JENKINS-17269) 10 Testcases fail on Windows with error: hudson.util.IOException2: Failed to clean up temp dirs
Patrik Johansson commented on JENKINS-17269 10 Testcases fail on Windows with error: hudson.util.IOException2: Failed to clean up temp dirs Probably related to JENKINS-12328 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17269) 10 Testcases fail on Windows with error: hudson.util.IOException2: Failed to clean up temp dirs
Patrik Johansson closed JENKINS-17269 as Duplicate 10 Testcases fail on Windows with error: hudson.util.IOException2: Failed to clean up temp dirs Change By: Patrik Johansson (19/Mar/13 3:14 PM) Status: Open Closed Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17235) No error message displayed even on failure if I try to run the same job with same params in parallel
Patrik Johansson
created JENKINS-17235
No error message displayed even on failure if I try to run the same job with same params in parallel
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
build-flow
Created:
15/Mar/13 4:20 PM
Description:
If I run the following flow script all goes well:
parallel (
{ build("Job1", param:1); build("Job2", param:1) },
{ build("Job1", param:2); build("Job2", param:2) }
)
However, when I change it so that I try to run the same job twice, in parallel, with the same params, the build flow job fails without any error traces in the log. So the following script:
parallel (
{ build("Job1", param:1); build("Job2", param:1) },
{ build("Job1", param:1); build("Job2", param:1) }
)
gives the following console output (and a FAILED status):
Started by user anonymous
Building in workspace C:\xxx\.jenkins\jobs\Flow1\workspace
parallel {
Trigger job Job1
Trigger job Job1
Job1 #15 completed
Trigger job Job2
Job2 #12 completed
}
Collecting metadata...
Metadata collection done.
Finished: FAILURE
It would help alot if there was a clear error message saying something like: "Could not run parallel job 'Job1' since identical instances of it were scheduled"
Environment:
Jenkins 1.505, Windows Vista, Build Flow 0.8
Project:
Jenkins
Priority:
Major
Reporter:
Patrik Johansson
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17213) Slave threads crashed when trying to lock a resource without having set a root url for Jenkins
Patrik Johansson created JENKINS-17213 Slave threads crashed when trying to lock a resource without having set a root url for Jenkins Issue Type: Bug Affects Versions: current Assignee: rsandell Attachments: error.log Components: external-resource-dispatcher Created: 14/Mar/13 11:58 AM Description: If I configure my job to use external resource selection criteria without first having reconfigured the Jenkins url I get the error below (also see attachment). In other words the url under Manage Jenkins/ Configure System/Jenkins url is set to http://localhost:8080 when this error occurs. If I change the url to something else (say http://test:8080) the error doesn't occur. The effect is that all build threads on the current slave server die with this error message: Exception in thread "Executor #1 for master" java.lang.IllegalStateException: Root URL isn't configured yet. Cannot compute absolute URL. at hudson.model.AbstractItem.getAbsoluteUrl(AbstractItem.java:419) at com.sonyericsson.jenkins.plugins.externalresource.dispatcher.ExternalResourceQueueTaskDispatcher.getUrl(ExternalResourceQueueTaskDispatcher.java:176) at com.sonyericsson.jenkins.plugins.externalresource.dispatcher.ExternalResourceQueueTaskDispatcher.canTake(ExternalResourceQueueTaskDispatcher.java:122) at hudson.model.Queue$JobOffer.canTake(Queue.java:254) at hudson.model.Queue.maintain(Queue.java:1032) at hudson.model.Queue.pop(Queue.java:863) at hudson.model.Executor.grabJob(Executor.java:285) at hudson.model.Executor.run(Executor.java:206) Environment: Linux Mint, Jenkins 1.505, External Resource Dispatcher 1.0b Project: Jenkins Labels: plugin Priority: Minor Reporter: Patrik Johansson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17098) Wipe out workspace does not remove parallel workspaces correctly
Patrik Johansson created JENKINS-17098 Wipe out workspace does not remove parallel workspaces correctly Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 06/Mar/13 10:02 AM Description: I have a job that allows parallel runs which frequently leads to a number of workspaces being creted. After running it a few times I have the following file structure: jenkins-home/jobs/job1/ workspace workspace@2 workspace@3 workspace@4 If I run "Wipe Out Workspace" it seems as if Jenkins chooses a random directory of the 4 to wipe out (possibly based on which one was used last). So sometimes it will remove the "workspace" directory, and leave the other 3 and sometimes it will remove one of the others (like workspace@2). It never seems to remove all of them though. Environment: Jenkins 1.504 on Windows Vista and Jenkins 1.497 on SUSE Linux Project: Jenkins Priority: Major Reporter: Patrik Johansson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16135) Build Flow dependency graph doesn't render on job status page
Patrik Johansson commented on JENKINS-16135 Build Flow dependency graph doesnt render on job status page Shouldn't this ticket be closed now, seeing how it is no longer relevant after Pull req. https://github.com/jenkinsci/build-flow-plugin/pull/20 was accepted and released in v0.8? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12188) GIT plug-ins keep lock on workspace file if branch use default insted of master. So unable to clean workspace.
Patrik Johansson commented on JENKINS-12188 GIT plug-ins keep lock on workspace file if branch use default insted of master. So unable to clean workspace. I am seeing the same problem. Would anyone have the possibility to include the patch into the coming release? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
