Verify that Android-specific task data is ingested by the `testselect` model
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 570
- Forks
- 351
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 65
Description
There's a belief -- perhaps unjustified -- in the Firefox for Android engineering team that mach try auto "does not work" for Android development. Certainly mach try auto pushes like this one, which modified many build.gradle files, don't kick off Android-specific jobs like build-components or test-components or Fenix-specific UI test jobs. (It did kick off a gvjunit job.)
This ticket tracks verifying that the new, fairly non-standard, Android tasks are being ingested by the appropriate models, so that Firefox for Android engineers can use mach try auto fearlessly. Hopefully, exclusively!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with mach try auto, the testselect model, and the linked Treeherder try push as the reproduction case. Check whether build-components, test-components, and Fenix-specific UI test tasks are ingested, and establish whether the Android task data reaches the appropriate models.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, python
- Domain
- devtools, machine-learning, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100