Open Bug 1758171 Opened 7 months ago Updated 2 months ago

Release list is breaking chronological order

Categories

(Testing :: mozregression, defect, P3)

Default
defect

Tracking

(Not tracked)

People

(Reporter: jaso35, Unassigned)

Details

Attachments

(1 file)

Currently, the release list seems to be built by appending a fetched list of releases in antichronological order to a predetermined chronological one. This leads to a release list that suddenly changes order.

This can easily be seen by running mozregression --list-releases

Current output:

Valid releases: 
  5: 2011-04-12
  6: 2011-05-24
[...]
 55: 2017-06-12
 56: 2017-08-02
 98: 2022-02-07 <!--- Order suddenly turns antichronological here
 97: 2022-01-10
 96: 2021-12-07
 95: 2021-11-01
 [...]
 58: 2017-11-12
 57: 2017-09-21

Expected output:

Valid releases: 
  5: 2011-04-12
  6: 2011-05-24
 [...]
 55: 2017-06-12
 56: 2017-08-02
 57: 2017-09-21
 58: 2017-11-12
 59: 2018-01-21
 60: 2018-03-12
 [...]
 97: 2022-01-10
 98: 2022-02-07

This should be simple to fix by reversing the order of fetched releases before building the list. I will attach a patch.

The severity field is not set for this bug.
:zeid, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(zeid)
Severity: -- → S4
Flags: needinfo?(zeid)
Priority: -- → P3

The bug assignee is inactive on Bugzilla, so the assignee is being reset.

Assignee: jaso35 → nobody
You need to log in before you can comment on or make changes to this bug.