Closed Bug 1735398 Opened 3 years ago Closed 2 years ago

Update and move the FFMPEG binaries out of the non-standard repo that they are in

Categories

(Testing :: Raptor, task, P1)

task

Tracking

(firefox107 fixed)

RESOLVED FIXED
107 Branch
Tracking Status
firefox107 --- fixed

People

(Reporter: sparky, Assigned: aglavic)

References

(Blocks 1 open bug)

Details

(Whiteboard: [fxp])

Attachments

(1 file)

Currently, the FFMPEG binaries are housed in a user's repository: https://github.com/ncalexan/geckodriver/releases/download/v0.24.0-android/ffmpeg-4.1.4-i686-static.tar.xz

We should move these to a standard location like tooltool or to a mozilla github repo.

Blocks: dev-pain

We also should update FFMPEG to the latest compatible version, especially considering the issue discovered via bug 1771977. We could use https://github.com/mozilla/perf-automation to store the binaries instead of Nick's fork of the geckodriver repository. Otherwise, we could consider other options for retrieving the binaries such as tooltool.

Severity: S4 → S3
Priority: P2 → P1
Summary: Move the FFMPEG binaries out of the non-standard repo that they are in → Update and move the FFMPEG binaries out of the non-standard repo that they are in
Assignee: nobody → aglavic

What we are doing:

  • Upgrading FFMPEG version from 4.1.4 to 4.4.1
  • Moving the binaries out of a personal github to the perf-automation mozilla repository
Pushed by aglavic@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/958cce6ed991
Update and move the FFMPEG binaries out of the non-standard repository. r=perftest-reviewers,sparky
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 107 Branch
Regressions: 1795240
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: