/srv/irclogs.ubuntu.com/2015/03/23/#launchpad-dev.txt

cjwatsonwgrant: builder processor sorting> do you mean on id or (contrary to the current UI) alphabetically by processor name?12:38
wgrantcjwatson: Anything that's deterministic, but name might be sensible.12:39
cjwatsonThe overall sort key should probably remain id, so that x86 builders land at the top.12:42
wgrantIndeed.12:42
cjwatsonAlthough I guess that would still be the case since amd64 is lexicofirst12:42
cjwatsonBut might not always be, who knows.12:42
wgrantLucky we don't have aarch64.12:42
infinityAardvarch.12:47
infinityI guess we have no concept of sort-of-related processor families?12:47
infinityCause it would be nice for amd64/i386 to sort together, arm64/armhf/armel, ppc64el/ppc64/powerpc12:48
wgrantNot at the moment.12:48
wgrantBut in practise they will eventually be grouped.12:48
infinityYeah, fair.12:48
infinityOnce they're all grouped, I guess that'll sort (hah!) itself.12:48
cjwatsonwgrant: Actually, this *is* the overall sort key.12:49
cjwatsonSo if we're doing this in that method it might as well just be sorted(p.name for p in builder.processors)12:49
wgrantcjwatson: Oh, is builder.processors sorted already?12:50
cjwatsonBy id12:50
cjwatson        return list(Store.of(self).find(12:51
cjwatson            Processor,12:51
cjwatson            BuilderProcessor.processor_id == Processor.id,12:51
cjwatson            BuilderProcessor.builder == self).order_by(Processor.id))12:51
cjwatsonwgrant: Does that address your MP comment, then?  I thought you knew about that and wanted it explicit in the browser code too.12:56
cjwatsonI could add a comment indicating the sorting.12:56
wgrantcjwatson: I think it's fine as it is. I hadn't realised the property was explicitly sorted already.12:57
cjwatsonOK12:58

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!