AbstractDotNetTestReportCollector used single non thread safe parser instance to handle async calls to collect method. It caused a huge problem when multiple test files were parsed.
[BAM-9197] ThreadSafe issues in AbstractDotNetTestReportCollector
Workflow | Original: Bamboo Workflow 2016 v1 - Restricted [ 1434929 ] | New: JAC Bug Workflow v3 [ 3378692 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Bamboo Workflow 2016 v1 [ 1409205 ] | New: Bamboo Workflow 2016 v1 - Restricted [ 1434929 ] |
Workflow | Original: Bamboo Workflow 2014 v2 [ 613773 ] | New: Bamboo Workflow 2016 v1 [ 1409205 ] |
Workflow | Original: Bamboo Workflow 2014 [ 598810 ] | New: Bamboo Workflow 2014 v2 [ 613773 ] |
Workflow | Original: Bamboo Workflow 2010 [ 305377 ] | New: Bamboo Workflow 2014 [ 598810 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: To be reviewed [ 10026 ] | New: Resolved [ 5 ] |
Status | Original: In Progress [ 3 ] | New: To be reviewed [ 10026 ] |
Internal Priority | New: 2. High [ 10286 ] |
Description | Original: AbstractDotNetTestReportCollector used single non thread safe parser instance to handle async calls to collect method. It caused a huge fuckup when multiple test files were parsed. | New: AbstractDotNetTestReportCollector used single non thread safe parser instance to handle async calls to collect method. It caused a huge problem when multiple test files were parsed. |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |