Low Steps to reproduce
- In the default job, create task to checkout a repository that has no any test result files
- Create a script task that will create or copy a test result file to the build working directory. See screenshot script.png
- Create a Junit parser task to parse the result files created in step 2 above.
- The build fails with the error "Could not find test result reports in the ...."
This same configuration worked in Bamboo 4.1 but fails in later versions of 4.3.x
[BAM-12671] JUNIT parser ignores test results created/provided from preceeding tasks
| Workflow | Original: Bamboo Workflow 2016 v1 - Restricted [ 1443473 ] | New: JAC Bug Workflow v3 [ 3383838 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Bamboo Workflow 2016 v1 [ 1421523 ] | New: Bamboo Workflow 2016 v1 - Restricted [ 1443473 ] |
| Workflow | Original: Bamboo Workflow 2014 v2 [ 607168 ] | New: Bamboo Workflow 2016 v1 [ 1421523 ] |
Rostislav Pasechnikov
added a comment - Seem to be having the same problem with MSTest parser. Unable to pick up the .trx file generated.
Rostislav Pasechnikov
added a comment - Seem to be having the same problem with MSTest parser. Unable to pick up the .trx file generated. 
Emre Kutbay
added a comment - we still have this problem too: 05.2016, is there any way to switch off this behaviour?
Emre Kutbay
added a comment - we still have this problem too: 05.2016, is there any way to switch off this behaviour? 
Brian Johnson
added a comment - I still have this problem in Atlassian Bamboo version 5.9.2 build 5917 - 09 Jul 15
When will there be a concrete work around or fix for this?
Have tried all known work arounds with no success
Brian Johnson
added a comment - I still have this problem in Atlassian Bamboo version 5.9.2 build 5917 - 09 Jul 15
When will there be a concrete work around or fix for this?
Have tried all known work arounds with no success | Workflow | Original: Bamboo Workflow 2014 [ 595023 ] | New: Bamboo Workflow 2014 v2 [ 607168 ] |
| Workflow | Original: Bamboo Workflow 2010 [ 458845 ] | New: Bamboo Workflow 2014 [ 595023 ] |
I'm having this problem using JUnit Parser on 5.14. In my case I am passing the xml file from one stage to the next as an artifact. Is this not exactly what artifacts are for?
To fix it you could have the artifact copy for a given stage touch the file so that its timestamp is after the start of the stage.
Better yet, if your goal is to avoid picking up files from previous builds, why not check their time vs. the start of the build rather than the start of the stage?