Red Hat Bugzilla – Bug 836950
matrix report inconsistent column ordering
Last modified: 2016-09-15 03:04:01 EDT
Description of problem: See this report: https://beaker.engineering.redhat.com/matrix/?toggle_nacks_on=on&job_ids=255568+255509+255508+255543+255542+255545 The order of old/new columns differ from architecture to architecture. Could beaker enforce the same order for all columns? Preferably old left, new right - that's what we're use to. Thanks Version-Release number of selected component (if applicable): 0.9
Sorting the columns in an alphabetical order would be best (and simple to implement, I presume). Check this (one heck of a) matrix report: https://beaker.engineering.redhat.com/matrix/?toggle_nacks_on=on&job_ids=302238+302239 Currently the columns are (from left to right): 3 - AS - old 4 - AS - old 5.3.ll - Server - old ... ... 3 - AS - new 4 - AS - new 5.3.ll - Server - new ... ... Expected results: 3 - AS - old 3 - AS - new 4 - AS - old 4 - AS - new 5.3.ll - Server - old 5.3.ll - Server - new ... ... This way both old and new results from one particular RHEL version are next to each other - checking for regressions is easy.
Alphabetical order would be simplest and easiest I'd think, but then you would end up with '10.x.y' coming before '5.3.ll' for example. So we probably want to do numerical + alphabetical sorting, I'm assuming that would be preferrable ?
yes, you're right (Also lately I have been studying this alphabet thing; it turns out that 'o' comes after 'n'. Which will mean, contrary to my previous comment, that when sorted alphabetically new jobs will come before old ones. But that's just a very minor inconvenience and I'm ok with it).