Bug 1575213 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Now that we have the ability to run "shadow schedulers", we should create an optimizer that tries to use code coverage information.

Marco has set up a database that exists as an artifact [here](https://index.taskcluster.net/v1/task/project.releng.services.project.production.code_coverage_bot.latest/artifacts/public/chunk_mapping.tar.xz).

This is a sqlite database that has a table called `file_to_chunk` which is a mapping of "source file" -> "test task". Our optimizer can download this, check if any of the modified files can be mapped to test tasks, and remove any tasks that aren't in the list.
Now that we have the ability to run "shadow schedulers", we should create an optimizer that tries to use code coverage information.

Marco has set up a database that exists as an artifact [here](https://index.taskcluster.net/v1/task/project.releng.services.project.production.code_coverage_bot.latest/artifacts/public/chunk_mapping.tar.xz).

This is a sqlite database that has a table called `file_to_chunk` which is a mapping of "source file" -> "test task". Our optimizer can download this, check if any of the modified files can be mapped to test tasks, and remove any tasks that aren't in the list.

Much of the logic we'll need is already implemented in the [try coverage](https://searchfox.org/mozilla-central/source/tools/tryselect/selectors/coverage.py) selector. Once we fix this bug, we should refactor that selector to import the optimizer from `taskgraph` and use that.

Back to Bug 1575213 Comment 0