Open Bug 1798974 Opened 3 years ago Updated 2 years ago

[meta] Modify how benchmarks are run

Categories

(Testing :: Raptor, task, P3)

task

Tracking

(Not tracked)

People

(Reporter: sparky, Assigned: sparky)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

(Keywords: meta, Whiteboard: [fxp])

Currently, the method we use for running benchmarks is quite inflexible. It requires us to make releases in the perf-automation repo: https://github.com/mozilla/perf-automation

It suffices to say that the process is convoluted for developers to use if they want to easily test updates to their benchmarks (such as matrix-react, or the twitch benchmark). On top of that, we can't get these built automatically in CI.

This bug is for two things:
(1) Modifying how the benchmarks are pulled in from repositories, and
(2) Adding the ability to run a build task for the tools (similar to what we do for browsertime).

In CI, we are almost ready for allowing non perf-automation benchmarks to be used but locally, we need to fix up mach_commands to let it pull from other repos whose location may be defined in the INI files.

Severity: -- → S3
Priority: -- → P3
Summary: Modify how benchmarks are run → [meta] Modify how benchmarks are run
Depends on: 1804453
Depends on: 1804577
Depends on: 1804578
Blocks: 1548505
Depends on: 1804694
You need to log in before you can comment on or make changes to this bug.