[JIRA] [core] (JENKINS-18626) Incorrect age in the test results
Louis Roché created JENKINS-18626 Incorrect age in the test results Issue Type: Bug Affects Versions: current Assignee: Manuel Carrasco Components: core, performance-plugin Created: 05/Jul/13 7:41 AM Description: I have a matrix with many cases who generate some JUnit reports. These reports are read by the performance plugin. When I go in the Test Results page, there is an age column. The ages in this column are not correct and change sometimes with reason. For example, the build 26616 contain a test who fail for the past 164 builds. But Jenkins don't always says that. Sometimes it says that the age is 26617. When I have the problem, I should follow the "Previous Build" links to come back to first failure of the test. And then when I click on "Next Build", the age is the good one. Project: Jenkins Labels: results junit age Priority: Critical Reporter: Louis Roché 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] [core] (JENKINS-18626) Incorrect age in the test results
Louis Roché updated JENKINS-18626 Incorrect age in the test results Change By: Louis Roché (05/Jul/13 7:42 AM) Description: IhaveamatrixwithmanycaseswhogeneratesomeJUnitreports.Thesereportsarereadbytheperformanceplugin.WhenIgointheTestResultspage,thereisanagecolumn.Theagesinthiscolumnarenotcorrectandchangesometimeswith no reason.Forexample,thebuild26616containatestwhofailforthepast164builds.ButJenkinsdontalwayssaysthat.Sometimesitsaysthattheageis26617.WhenIhavetheproblem,IshouldfollowthePreviousBuildlinkstocomebacktofirstfailureofthetest.AndthenwhenIclickonNextBuild,theageisthegoodone. 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] [xunit] (JENKINS-18575) xUnit failed to parse a JUnit .xml report without any debug in log
Louis Roché commented on JENKINS-18575 xUnit failed to parse a JUnit .xml report without any debug in log I have the same problem after the upgrade of the plugin from 1.57 or 1.58 (I don't remember). Performance plugin read the file without problem. 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] [matrix-reloaded] (JENKINS-17964) NPE if one of the upstream builds is not found
Louis Roché created JENKINS-17964 NPE if one of the upstream builds is not found Issue Type: Bug Affects Versions: current Assignee: Praqma Support Components: matrix-reloaded Created: 15/May/13 2:29 PM Description: I have a nightly build who trigger a matrix and I have this error for every jobs in the matrix: Started by upstream project "Windows Results" build number 12418 originally caused by: Started by upstream project "Supervisor Test Windows Nightly" build number 615 originally caused by: Started by upstream project "Nightly Build Hoops 3DX main line Windows 64" build number 541 originally caused by: Started by an SCM change Building remotely on Slave2 FATAL: null java.lang.NullPointerException at net.praqma.jenkins.plugin.reloaded.Util.getUpstreamRebuildAction(Util.java:84) at net.praqma.jenkins.plugin.reloaded.Util.getDownstreamRebuildActionFromMatrixBuild(Util.java:63) at net.praqma.jenkins.plugin.reloaded.MatrixReloadedEnvironmentContributor.buildEnvironmentFor(MatrixReloadedEnvironmentContributor.java:44) at hudson.model.Run.getEnvironment(Run.java:2045) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:931) at hudson.matrix.MatrixRun$MatrixRunExecution.decideWorkspace(MatrixRun.java:175) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:567) at hudson.model.Run.execute(Run.java:1575) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) I don't have the problem with the daily build who trigger not all jobs in the matrix. So I was thinking about a heavy load problem, but it seems to be something different. the 3 upstream projects are still in jenkins. https://groups.google.com/forum/#!topic/jenkinsci-users/nXQQ0yLg238 Environment: windows 7 jenkins 1.511 Project: Jenkins Labels: plugin matrix exception Priority: Critical Reporter: Louis Roché 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] [matrix-reloaded] (JENKINS-17964) NPE if one of the upstream builds is not found
Louis Roché
updated JENKINS-17964
NPE if one of the upstream builds is not found
Change By:
Louis Roché
(15/May/13 2:34 PM)
Description:
IhaveanightlybuildwhotriggeramatrixandIhavethiserrorforeveryjobsinthematrix:{code}StartedbyupstreamprojectWindowsResultsbuildnumber12418originallycausedby:StartedbyupstreamprojectSupervisorTestWindowsNightlybuildnumber615originallycausedby:StartedbyupstreamprojectNightlyBuildHoops3DXmainlineWindows64buildnumber541originallycausedby:StartedbyanSCMchangeBuildingremotelyonSlave2FATAL:nulljava.lang.NullPointerException atnet.praqma.jenkins.plugin.reloaded.Util.getUpstreamRebuildAction(Util.java:84) atnet.praqma.jenkins.plugin.reloaded.Util.getDownstreamRebuildActionFromMatrixBuild(Util.java:63) atnet.praqma.jenkins.plugin.reloaded.MatrixReloadedEnvironmentContributor.buildEnvironmentFor(MatrixReloadedEnvironmentContributor.java:44) athudson.model.Run.getEnvironment(Run.java:2045) athudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:931) athudson.matrix.MatrixRun$MatrixRunExecution.decideWorkspace(MatrixRun.java:175) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:567) athudson.model.Run.execute(Run.java:1575) athudson.matrix.MatrixRun.run(MatrixRun.java:146) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:237){code}Idonthavetheproblemwiththedailybuildwhotriggernotalljobsinthematrix.SoIwasthinkingaboutaheavyloadproblem,butitseemstobesomethingdifferent.the3upstreamprojectsarestillinjenkins.
Butnoteveryworkspaces.
https://groups.google.com/forum/#!topic/jenkinsci-users/nXQQ0yLg238
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-16827) console display wrong build number when triggering a new build
Louis Roché updated JENKINS-16827 console display wrong build number when triggering a new build Change By: Louis Roché (21/Feb/13 10:08 AM) Component/s: all-changes 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-16827) console display wrong build number when triggering a new build
Louis Roché created JENKINS-16827 console display wrong build number when triggering a new build Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: downstreambuildview.png Components: core Created: 15/Feb/13 3:23 PM Description: I have a build which can trigger another build. In the console, I have at the end of the log: Triggering a new build of Build Hoops 3DX 5_x Windows Samples #1758 Triggering a new build of Supervisor Test Windows Continuous #2831 But I have not the same informations in Downstream build view. The good informations are in the Downstream build view. Environment: Jenkins server on windows 7 64. Slaves on windows 7 32/64. Project: Jenkins Priority: Major Reporter: Louis Roché 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.
