Yes, that would probably work. I'm not sure if buildbot is flexible
enough to handle that kind of scheduling. cc'ing catlee.
Jonathan
On 2/1/2013 2:42 PM, John Ford wrote:
Instead of using Nightly, could you use the last green test run's Gaia master
branch commit id as the replacement for a nightly branch commit id?
John
On Feb 1, 2013, at 1:26 PM, Jonathan Griffin wrote:
https://bugzilla.mozilla.org/show_bug.cgi?id=834354
On 2/1/2013 1:22 PM, John Ford wrote:
That only works if code gets uplifted to nightly regularly, which it isn't any
more.
What's the bug tracking the fixes to automation -- can we prioritize these
fixes?
On Feb 1, 2013, at 1:11 PM, [email protected] wrote:
Regarding TBPL tests, the removal of nightly will be problematic for sheriffing.
Currently, we run Gaia UI tests per gecko commit, not per gaia commit. (We
have plans to do the latter, but it's a little complicated getting it hooked
up.)
On each gecko commit, we run the tests twice, once against gaia's master branch
and once against gaia's nightly branch. If a test breaks against both, the
sheriffs can assume it is a gecko problem. If a test breaks only against
gaia's master branch, but not against gaia's nightly branch, then sheriffs can
assume it's a gaia problem.
Without gaia's nightly branch, we won't be able to make that distinction;
sheriffs will have no way to know if a bustage is caused by a gecko or gaia
commit, which will effectively make them unsheriffable, at least until we get
tests running per-commit to gaia.
Can we postpone this change until buildbot is capable of running Gaia tests
per-Gaia-commit?
Jonathan
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
