| 2009-01-26 19:22:20 |
Daniel Hahler |
bug |
|
|
added bug |
| 2009-01-26 19:35:24 |
Celso Providelo |
launchpad: bugtargetdisplayname |
Launchpad itself |
Soyuz |
|
| 2009-01-26 19:35:24 |
Celso Providelo |
launchpad: bugtargetname |
launchpad |
soyuz |
|
| 2009-01-26 19:35:24 |
Celso Providelo |
launchpad: statusexplanation |
|
|
|
| 2009-01-26 19:35:24 |
Celso Providelo |
launchpad: title |
Bug #321584 in Launchpad itself: "Do not sort unknown dates to the top in list of builds (+builds)" |
Bug #321584 in Soyuz: "Do not sort unknown dates to the top in list of builds (+builds)" |
|
| 2009-07-22 12:09:13 |
Julian Edwards |
tags |
soyuz-build ui |
soyuz-build |
|
| 2009-07-22 12:09:22 |
Julian Edwards |
soyuz: status |
New |
Triaged |
|
| 2009-07-22 12:09:25 |
Julian Edwards |
soyuz: importance |
Undecided |
Medium |
|
| 2011-10-01 21:12:32 |
Robert Collins |
description |
The list of failed builds [1] gets sorted so that the first entries (> 225 currently) state:
"Build started at an unknown time on an unknown build machine"
Since it's most interesting to see what failed recently, the newest entries (with known date), should get sorted to the top; and the unknown ones probably to the end.
1: https://edge.launchpad.net/ubuntu/+builds?build_text=&build_state=failed&start=225&batch=75 |
The list of failed builds [1] gets sorted so that the first entries (> 225 currently) state:
"Build started at an unknown time on an unknown build machine"
Since it's most interesting to see what failed recently, the newest entries (with known date), should get sorted to the top; and the unknown ones probably to the end.
1: https://launchpad.net/ubuntu/+builds?build_text=&build_state=failed&start=225&batch=75 |
|
| 2011-10-01 21:14:20 |
Robert Collins |
summary |
Do not sort unknown dates to the top in list of builds (+builds) |
FTBFS (+builds?build_state=failed) list unhelpful for folk fixing failures |
|
| 2011-10-01 21:16:27 |
Robert Collins |
description |
The list of failed builds [1] gets sorted so that the first entries (> 225 currently) state:
"Build started at an unknown time on an unknown build machine"
Since it's most interesting to see what failed recently, the newest entries (with known date), should get sorted to the top; and the unknown ones probably to the end.
1: https://launchpad.net/ubuntu/+builds?build_text=&build_state=failed&start=225&batch=75 |
The list of failed builds [1] gets sorted so that the first entries (> 225 currently) state:
"Build started at an unknown time on an unknown build machine"
Since it's most interesting to see what failed recently, the newest entries (with known date), should get sorted to the top; and the unknown ones probably to the end.
1: https://launchpad.net/ubuntu/+builds?build_text=&build_state=failed&start=225&batch=75
Analysis
========
The build list serves many users, but the failed build list is really for folk fixing FTBFS issues, so tweaking the sort to help them makes sense. The unknowns seem to be security builds, which suggests either a permissions issue (why are we showing them?!) or if not that then it looks like NULLS FIRST in the sort order. Some query spelunking needed.
However a better way to address this might be a FTBFS report which only shows current failures (vs the build list which will show a failure even if the package has subsequently been biult). |
|
| 2011-10-01 21:16:31 |
Robert Collins |
launchpad: importance |
Medium |
Low |
|
