Open Bug 1570650 Opened 6 years ago Updated 1 year ago

mozregression should work with esr branches

Categories

(Testing :: mozregression, enhancement)

Version 3
enhancement

Tracking

(Not tracked)

People

(Reporter: denschub, Unassigned)

References

Details

I'm currently running into an issue with the Fenenc "esr" builds I need to run mozregression on, so I tried --repo mozilla-esr68 and other combinations, to no avail. Looking at mozregression/branches.py, it looks like mozregression is not able to deal with esr, which it probably should.

So this is something I'd thought about adding before. I guess the question is if we want to hard-code known ESRs (and update once a year for new ones), or only provide current ones, which are query-able from firefox_versions.json. I'm leaning towards the latter, since I doubt there'd be much call for regression-testing no-longer-supported versions. First pass implementation: https://github.com/KwanEsq/mozregression/commit/esr

Assignee: nobody → moz-ian
Status: NEW → ASSIGNED

Sorry, there was a problem with the detection of inactive users. I'm reverting the change.

Assignee: nobody → moz-ian
Status: NEW → ASSIGNED
Severity: normal → S3

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

Assignee: moz-ian → nobody
Status: ASSIGNED → NEW

Today I need to test ESR 78.9. Writing this to say that it may happen that we need older versions. Hopefully this can be done.

You need to log in before you can comment on or make changes to this bug.