instrumented-build-macrobenchmark-apk-fenix is always running on autoland, and not actually used
Categories
(Firefox for Android :: Performance, defect)
Tracking
()
People
(Reporter: titouan, Unassigned)
References
(Blocks 1 open bug)
Details
We noticed that the instrumented-build-macrobenchmark-apk-fenix is always run on autoland, even if the job actually running macrobenchmark on FirebaseTestLab doesn't run.
This means we are building apks that are never used to actually run the benchmarks. We should make sure that this task only runs when we actually want to run macrobenchmark, to avoid wasting resources.
Here is an example showing it, but any try run on autoland would show the same kind of result.
This Taskcluster link shows that instrumented-build-macrobenchmark-apk-fenix is a dependent of the generate-baseline-profile-firebase-fenix task. But we need to understand why the dependent task is triggered.
The dependencies of the instrumented-build-macrobenchmark-apk are defined here.
Description
•