None
Recent failures
| Failed In | Fixed In | Time Taken To Fix | ||
|---|---|---|---|---|
| #844 |
Code changes detected
|
#847 |
Manual run by Cintia Del Rio
|
3 builds 4 hours, 23 minutes |
| #745 |
Child of AF-AF-265
|
#747 |
Code changes detected
|
2 builds 2 days, 15 hours, 46 minutes |
| #740 |
Child of AF-AF-262
|
#741 |
Manual run by Daniel Kayiwa
|
1 build 44 minutes |
| #390 |
Code changes detected
|
#391 |
Code changes detected
|
1 build 8 minutes |
| #279 |
Child of UIFR-UIFR-138
|
#280 |
Child of PMM-PMM-148
|
1 build 5 minutes |
| #219 |
Code changes detected
|
#220 |
Code changes detected
|
1 build 6 minutes |
| #186 |
Child of TRUNK-LATEST-150
|
#187 |
Child of TRUNK-LATEST-151
|
1 build 23 hours, 54 minutes |
| #149 |
Code changes detected
|
#150 |
Code changes detected
|
1 build 47 minutes |
| #133 |
Child of TRUNK-LATEST-134
|
#138 |
Code changes detected
|
5 builds 5 days, 19 hours, 40 minutes |
- Average time to fix a failure: 1 day, 1 hour, 57 minutes
- Average number of builds between fixes: 1.78 builds
- The longest time taken to fix a failure is 5 days, 19 hours, 40 minutes, from failure starting in build #133.
- The greatest number of builds taken to fix a failure is 5, from failure starting in build #133.