Comment 1 for bug 889861

At the moment we use some heuristics to try to avoid this sort of situation, in particular, we avoid known problems such as device/*, toolchain/* and so on.

There's no guarantee that the manifest we use for testing contains the project the change is in. There's also no reliable way to work out what manifest we should be using, or if we should be adding the project to a .repo/local_manifest.xml.

I'll create a BP to investigate better ways to deal with projects that only appear in a subset of release manifests.