Recent failures
Failed In | Fixed In | Time Taken To Fix | ||
---|---|---|---|---|
#106 |
Code changes detected
|
#107 |
Code changes detected
|
1 build 29 minutes |
#95 |
Code changes detected
|
#96 |
Code changes detected
|
1 build 21 hours, 32 minutes |
#83 |
Code changes detected
|
#84 |
Manual run from the stage: Release by Samuel Male
|
1 build 20 minutes |
#74 |
Code changes detected
|
#75 |
Manual run by Daniel Kayiwa
|
1 build 1 hour, 41 minutes |
#59 |
Code changes detected
|
#61 |
Code changes detected
|
2 builds 2 hours, 57 minutes |
#56 |
Code changes detected
|
#58 |
Manual run by Rafal Korytkowski
|
2 builds 2 hours, 40 minutes |
#52 |
Rebuilt by Dimitri R
|
#54 |
Manual run from the stage: Release by Daniel Kayiwa
|
2 builds 1 day, 2 hours, 2 minutes |
#46 |
Manual run by Daniel Kayiwa
|
#47 |
Code changes detected
|
1 build 1 day, 6 hours, 2 minutes |
#22 |
Code changes detected
|
#23 |
Manual run by Rafal Korytkowski
|
1 build 21 hours, 8 minutes |
#17 |
Code changes detected
|
#18 |
Manual run from the stage: Release by Darius Jazayeri
|
1 build 44 minutes |
#13 |
Code changes detected
|
#14 |
Code changes detected
|
1 build 39 minutes |
#8 |
Manual run by Darius Jazayeri
|
#11 |
Manual run by Darius Jazayeri
|
3 builds 18 hours, 26 minutes |
- Average time to fix a failure: 10 hours, 33 minutes
- Average number of builds between fixes: 1.42 builds
- The longest time taken to fix a failure is 1 day, 6 hours, 2 minutes, from failure starting in build #46.
- The greatest number of builds taken to fix a failure is 3, from failure starting in build #8.