-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Closed
Labels
P1High-priority issues at the top of the work listHigh-priority issues at the top of the work listinfra: device labInfrastructure device lab problemsInfrastructure device lab problemsteam-infraOwned by Infrastructure teamOwned by Infrastructure teamtriaged-infraTriaged by Infrastructure teamTriaged by Infrastructure team
Description
Linux_android hot_mode_dev_cycle_linux__benchmark runs on a linux-motog4 bot, and runs in presubmit.
Lines 2394 to 2401 in 55d8b20
| # linux motog4 benchmark | |
| - name: Linux_android hot_mode_dev_cycle_linux__benchmark | |
| recipe: devicelab/devicelab_drone | |
| timeout: 60 | |
| properties: | |
| tags: > | |
| ["devicelab", "android", "linux"] | |
| task_name: hot_mode_dev_cycle_linux__benchmark |
However, there is only one of these bots in the try pool.
https://chromium-swarm.appspot.com/task?id=685d3bbc1eacaf10&o=true&w=true
https://chromium-swarm.appspot.com/botlist?f=os%3ALinux&f=pool%3Aluci.flutter.try&f=device_type%3Amsm8952

That means PRs are all bottlenecked on one bot. And if that bot dies all the PRs will be pending until it comes back up.
Either:
- Add more linux-motog4 bots to the try pool
- Stop running this test in presubmit
Metadata
Metadata
Assignees
Labels
P1High-priority issues at the top of the work listHigh-priority issues at the top of the work listinfra: device labInfrastructure device lab problemsInfrastructure device lab problemsteam-infraOwned by Infrastructure teamOwned by Infrastructure teamtriaged-infraTriaged by Infrastructure teamTriaged by Infrastructure team