Hi,
I've been noticing that the number of builds + tests we run on certain
changesets could still do with improving. I realize that we try to be
conservative because we don't want "magically appearing" orange, but I
still think that it should be possible to do better here. That seems
like it might also help with recent capacity problems (maybe?).
I don't know who's responsible for improving this, so I'm just posting
this here. The list is biased towards frontend desktop work because that
is what I do. Perhaps other people can provide further examples or
insight from android, b2g, platform, releng or sheriff perspectives into
what could/couldn't be improved here.
Some examples:
(1)
https://treeherder.mozilla.org/#/jobs?repo=fx-team&revision=0fd6c4c24dc9
This checkin only touched a single test file in
browser/components/preferences/in-content/tests/
It triggered browser builds on all platforms, but also all kinds of B2G
builds and tests, which are clearly useless, as well as running all
kinds of unrelated test suites for the browser builds.
Ideally, commits that only touch things in directories matching **test**
should only run the relevant test suite, if possible even with builds
from the previous rev.
(2)
https://treeherder.mozilla.org/#/jobs?repo=fx-team&revision=2b1d7ebb8325
This touched files in:
browser/base
browser/components
browser/locales
toolkit/obsolete/content
I don't think any of these are used outside Firefox for Desktop, and yet
android and b2g were built, too. The same happened with:
https://treeherder.mozilla.org/#/jobs?repo=fx-team&revision=80bd1ae9dd0a
which touched toolkit/content/widgets/ which AIUI is also desktop-only.
(3)
Checkins (couldn't find one offhand because summaries are little help in
identifying these) that only touch windows/linux/osx styles in browser/
and/or toolkit should only run those builds
~ Gijs
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
