Recent failures
Failed In | Fixed In | Time Taken To Fix | ||
---|---|---|---|---|
#186 |
Code changes detected
|
#187 |
Code changes detected
|
1 build 1 hour, 18 minutes |
#157 |
Code changes detected
|
#159 |
Code changes detected
|
2 builds 6 minutes |
#140 |
Code changes detected
|
#142 |
Manual run from the stage: Release by Herbert Yiga
|
2 builds 17 hours, 15 minutes |
#126 |
Manual run by Daniel Kayiwa
|
#127 |
Manual run from the stage: Release by Daniel Kayiwa
|
1 build 1 hour, 4 minutes |
#115 |
Code changes detected
|
#116 |
Manual run from the stage: Release by Daniel Kayiwa
|
1 build 7 minutes |
#78 |
Code changes detected
|
#80 |
Code changes detected
|
2 builds 1 hour, 26 minutes |
#69 |
Code changes detected
|
#70 |
Code changes detected
|
1 build 11 minutes |
#49 |
Code changes detected
|
#51 |
Manual run by Rafal Korytkowski
|
2 builds 2 days, 1 hour, 41 minutes |
#47 |
Code changes detected
|
#48 |
Code changes detected
|
1 build 24 minutes |
#45 |
Manual run by Rafal Korytkowski
|
#46 |
Manual run from the stage: Release by Rafal Korytkowski
|
1 build 5 minutes |
#42 |
Code changes detected
|
#43 |
Code changes detected
|
1 build 1 hour, 12 minutes |
#27 |
Code changes detected
|
#28 |
Code changes detected
|
1 build 12 minutes |
#24 |
Code changes detected
|
#25 |
Code changes detected
|
1 build 18 minutes |
#8 |
Manual run by Rafal Korytkowski
|
#9 |
Manual run from the stage: Release by Rafal Korytkowski
|
1 build 3 hours, 5 minutes |
#1 |
Manual run by Rafal Korytkowski
|
#7 |
Manual run from the stage: Release by Rafal Korytkowski
|
6 builds 26 minutes |
- Average time to fix a failure: 5 hours, 7 minutes
- Average number of builds between fixes: 1.6 builds
- The longest time taken to fix a failure is 2 days, 1 hour, 41 minutes, from failure starting in build #49.
- The greatest number of builds taken to fix a failure is 6, from failure starting in build #1.