[JIRA] (JENKINS-58430) Publishing two fitnesse xml files with same test name confuses the results
Title: Message Title jaruzafa updated JENKINS-58430 Fixed on fitnesse-plugin 1.30 Jenkins / JENKINS-58430 Publishing two fitnesse xml files with same test name confuses the results Change By: jaruzafa Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200559.1562773241000.1386.1568921340264%40Atlassian.JIRA.
[JIRA] (JENKINS-58430) Publishing two fitnesse xml files with same test name confuses the results
Title: Message Title jaruzafa updated JENKINS-58430 Jenkins / JENKINS-58430 Publishing two fitnesse xml files with same test name confuses the results Change By: jaruzafa Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200559.1562773241000.4332.1565992800389%40Atlassian.JIRA.
[JIRA] (JENKINS-58430) Publishing two fitnesse xml files with same test name confuses the results
Title: Message Title Johann Moro commented on JENKINS-58430 Re: Publishing two fitnesse xml files with same test name confuses the results Note that this issue probably needs to be reproduced on Linux because JENKINS-58923 will prevent you from reproducing this on Windows. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200559.1562773241000.4066.1565965380057%40Atlassian.JIRA.
[JIRA] (JENKINS-58430) Publishing two fitnesse xml files with same test name confuses the results
Title: Message Title jaruzafa started work on JENKINS-58430 Change By: jaruzafa Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200559.1562773241000.2218.1565735820304%40Atlassian.JIRA.
[JIRA] (JENKINS-58430) Publishing two fitnesse xml files with same test name confuses the results
Title: Message Title
Johann Moro updated an issue
Jenkins / JENKINS-58430
Publishing two fitnesse xml files with same test name confuses the results
Change By:
Johann Moro
* In one pipeline job, run the same FitNesse tests and generate 2 xml files. So for instance: ** FitNesse tests on Linux generates fitnesse_linux.xml ** FitNesse tests on Windows generates fitnesse_windows.xml The way the tests are generated is as follows (same for windows){code:java}java -jar ./fitnesse-standalone.jar -c "MySuite?suite=xml" -b fitnesse_windows.xml{code} * Now in the pipeline job, the tests are published in this way:{code:java}step([$class: 'FitnesseResultsRecorder', fitnessePathToXmlResultsIn: 'fitnesse_*.xml']){code} * Then let's assume that MySuite.TestOne fails on Linux, when I go to see the Details of the failure from the FitNesseReport link in Jenkins, while TestOne shows as failed, the html details I can see from there actually shows the details of the windows run.To reproduce this issue, use the following pipeline. Run it once and them manually copy the two xml files attached into the workspace. Run it again and it should publish the FitNesse results. My agent is a linux agent if that makes a difference. {code}pipeline {agent {label 'your-agent'}stages {stage ('Repro') {steps {echo 'Make sure the files are in the Workspace'}}}post {always {step([$class: 'FitnesseResultsRecorder', fitnessePathToXmlResultsIn: 'fitnesse_*.xml'])}}}{code}Once the results are published, you can see that the fitnesse_windows.xml has been successful while fitnesse_linux.xml has failed. You can see this in the FitNesse report that this is represented correctly: !FitNesseReport.png! !Details-of-test-not-representing-failure.png.png|thumbnail! But if I click on the fitnesse_linux.xml and then on the Details link for test _BuysideEnterprise.Ims.MySuite.TestOne_ then it actually shows me the details of the run in fitnesse_windows.xml instead of the linux one. It looks like the details have been overridden.Therefore, while I see that the test has failed, I cannot see why as it is showing me the incorrect run details: !Details-of-test-not-representing-failure.png!
[JIRA] (JENKINS-58430) Publishing two fitnesse xml files with same test name confuses the results
Title: Message Title Johann Moro updated an issue Jenkins / JENKINS-58430 Publishing two fitnesse xml files with same test name confuses the results Change By: Johann Moro Attachment: Details-of-test-not-representing-failure.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200559.1562773241000.7880.1562837400109%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58430) Publishing two fitnesse xml files with same test name confuses the results
Title: Message Title
Johann Moro updated an issue
Jenkins / JENKINS-58430
Publishing two fitnesse xml files with same test name confuses the results
Change By:
Johann Moro
* In one pipeline job, run the same FitNesse tests and generate 2 xml files. So for instance: ** FitNesse tests on Linux generates fitnesse_linux.xml ** FitNesse tests on Windows generates fitnesse_windows.xml The way the tests are generated is as follows (same for windows){code:java}java -jar ./fitnesse-standalone.jar -c "MySuite?suite=xml" -b fitnesse_windows.xml{code} * Now in the pipeline job, the tests are published in this way:{code:java}step([$class: 'FitnesseResultsRecorder', fitnessePathToXmlResultsIn: 'fitnesse_*.xml']){code} * Then let's assume that MySuite.TestOne fails on Linux, when I go to see the Details of the failure from the FitNesseReport link in Jenkins, while TestOne shows as failed, the html details I can see from there actually shows the details of the windows run.To reproduce this issue, use the following pipeline. Run it once and them manually copy the two xml files attached into the workspace. Run it again and it should publish the FitNesse results.{code}pipeline {agent {label 'your-agent'}stages {stage ('Repro') {steps {echo 'Make sure the files are in the Workspace'}}}post {always {step([$class: 'FitnesseResultsRecorder', fitnessePathToXmlResultsIn: 'fitnesse_*.xml'])}}}{code}Once the results are published, you can see that the fitnesse_windows.xml has been successful while fitnesse_linux.xml has failed. You can see this in the FitNesse report that this is represented correctly: !FitNesseReport.png! !Details-of-test-not-representing-failure.png.png|thumbnail! But if I click on the fitnesse_linux.xml and then on the Details link for test _BuysideEnterprise.Ims.MySuite.TestOne_ then it actually shows me the details of the run in fitnesse_windows.xml instead of the linux one. It looks like the details have been overridden.Therefore, while I see that the test has failed, I cannot see why as it is showing me the incorrect run details: !Details-of-test-not-representing-failure.png!
Add Comment
[JIRA] (JENKINS-58430) Publishing two fitnesse xml files with same test name confuses the results
Title: Message Title Johann Moro updated an issue Jenkins / JENKINS-58430 Publishing two fitnesse xml files with same test name confuses the results Change By: Johann Moro Attachment: FitNesseReport.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200559.1562773241000.7879.1562837220258%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58430) Publishing two fitnesse xml files with same test name confuses the results
Title: Message Title
Johann Moro updated an issue
Jenkins / JENKINS-58430
Publishing two fitnesse xml files with same test name confuses the results
Change By:
Johann Moro
* In one pipeline job, run the same FitNesse tests and generate 2 xml files. So for instance:** FitNesse tests on Linux generates fitnesse_linux.xml** FitNesse tests on Windows generates fitnesse_windows.xmlThe way the tests are generated is as follows (same for windows){code:java}java -jar ./fitnesse-standalone.jar -c "MySuite?suite=xml" -b fitnesse_windows.xml{code} * Now in the pipeline job, the tests are published in this way:{code:java} step([$class: 'FitnesseResultsRecorder', fitnessePathToXmlResultsIn: 'fitnesse_*.xml']){code} * Then let's assume that MySuite.TestOne fails on Linux, when I go to see the Details of the failure from the FitNesseReport link in Jenkins, while TestOne shows as failed, the html details I can see from there actually shows the details of the windows run. To reproduce this issue, use the following pipeline. Run it once and them manually copy the two xml files attached into the workspace. Run it again and it should publish the FitNesse results.{code}pipeline {agent {label 'your-agent'}stages {stage ('Repro') {steps {echo 'Make sure the files are in the Workspace'}}}post {always {step([$class: 'FitnesseResultsRecorder', fitnessePathToXmlResultsIn: 'fitnesse_*.xml'])}}}{code}Once the results are published, you can see that the fitnesse_windows.xml has been successful while fitnesse_linux.xml has failed. You can see this in the FitNesse report that this is represented correctly:
Add Comment
[JIRA] (JENKINS-58430) Publishing two fitnesse xml files with same test name confuses the results
Title: Message Title Johann Moro updated an issue Jenkins / JENKINS-58430 Publishing two fitnesse xml files with same test name confuses the results Change By: Johann Moro Attachment: fitnesse_linux.xml Attachment: fitnesse_windows.xml Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200559.1562773241000.7865.1562836860085%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58430) Publishing two fitnesse xml files with same test name confuses the results
Title: Message Title Johann Moro created an issue Jenkins / JENKINS-58430 Publishing two fitnesse xml files with same test name confuses the results Issue Type: Bug Assignee: Unassigned Components: fitnesse-plugin Created: 2019-07-10 15:40 Labels: plugin Priority: Major Reporter: Johann Moro In one pipeline job, run the same FitNesse tests and generate 2 xml files. So for instance: FitNesse tests on Linux generates fitnesse_linux.xml FitNesse tests on Windows generates fitnesse_windows.xml The way the tests are generated is as follows (same for windows) java -jar ./fitnesse-standalone.jar -c "MySuite?suite=xml" -b fitnesse_windows.xml Now in the pipeline job, the tests are published in this way: step([$class: 'FitnesseResultsRecorder',
